Triple
T3421272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Messages |
E72119
|
entity |
| Predicate | supportsProtocol |
P203
|
FINISHED |
| Object | RCS |
E123453
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: RCS | Statement: [Google Messages, supportsProtocol, RCS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCS Context triple: [Google Messages, supportsProtocol, RCS]
-
A.
RCS
chosen
RCS (Rich Communication Services) is a modern messaging protocol designed to replace SMS by supporting features like read receipts, high-quality media sharing, and enhanced group chats over mobile data.
-
B.
RCS
RCS is a leading conservatoire in Glasgow, Scotland, offering specialist education in music, drama, dance, production, and film.
-
C.
RSC
RSC is the commonly used abbreviation for the Royal Society of Canada, the national academy dedicated to promoting scholarly, scientific, and artistic excellence in Canada.
-
D.
RCN
RCN is the commonly used abbreviation for the Research Council of Norway, the national body responsible for funding and promoting research and innovation in Norway.
-
E.
RCN
RCN is the abbreviation for the Royal Canadian Navy, the maritime warfare branch of Canada’s armed forces.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb950f65481908c4aad15516e7a7c |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b35472881c8190baf90b91daa924ec |
completed | March 13, 2026, 12:04 a.m. |
Created at: March 8, 2026, 3:15 p.m.