Triple
T10802023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Island District |
E254860
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RID |
E254860
|
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: RID | Statement: [Rock Island District, abbreviation, RID]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RID Context triple: [Rock Island District, abbreviation, RID]
-
A.
RID
chosen
RID is the commonly used abbreviation for the Rock Island District, a commuter rail line serving the Chicago metropolitan area.
-
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.
RIC
RIC is the three-letter IATA airport code for Richmond International Airport, serving the Richmond, Virginia metropolitan area.
-
D.
RIC
RIC is the standard abbreviation used for the Richmond Flying Squirrels, a Minor League Baseball team based in Richmond, Virginia.
-
E.
RIC
RIC is a regulatory information circular or compliance framework reference used in the context of U.S. maritime safety and towing vessel regulations under Subchapter M.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7336dedec819099bd302c5d213dba |
completed | April 9, 2026, 5:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de566e7d408190946864e28c294075 |
completed | April 14, 2026, 2:59 p.m. |
Created at: April 8, 2026, 9:18 p.m.