Triple
T3144672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ici RDI |
E65734
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RDI |
E323517
|
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: RDI | Statement: [Ici RDI, abbreviation, RDI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RDI Context triple: [Ici RDI, abbreviation, RDI]
-
A.
RDI
chosen
RDI is a post-nominal title signifying membership in the Royal Designers for Industry, an elite British honor recognizing excellence in industrial design.
-
B.
RID
RID is the standard abbreviation for the Royal Institute Dictionary, the authoritative Thai language dictionary compiled by the Royal Institute of Thailand.
-
C.
RID
RID is the commonly used abbreviation for the Rock Island District, a commuter rail line serving the Chicago metropolitan area.
-
D.
RdR
RdR is the abbreviated name of the Council for German Orthography, the official body responsible for regulating and updating German spelling rules.
-
E.
RBD
RBD is the three-letter IATA airport code assigned to Dallas Executive Airport in Dallas, Texas.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada595d4548190b720a6131817833b |
completed | March 8, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b224ed4d748190a2af68bf284110e8 |
completed | March 12, 2026, 2:29 a.m. |
Created at: March 8, 2026, 3:05 p.m.