Triple
T2606576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 54 (Georgia) |
E58673
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 54 |
E58673
|
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: SR 54 | Statement: [SR 54 (Georgia), abbreviation, SR 54]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 54 Context triple: [SR 54 (Georgia), abbreviation, SR 54]
-
A.
SR 54
chosen
SR 54 is a state highway in Georgia that connects several communities in the western part of the state, including areas around Atlanta.
-
B.
SR 502
SR 502 is a state highway in New Mexico that serves as a key route connecting Los Alamos to other major roads in the region.
-
C.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
D.
SR 354
SR 354 is a state highway in Georgia that serves as a connector route in the western part of the state, providing access to local communities and regional roads.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd865c9908190be7e1b572a43972f |
completed | March 7, 2026, 7:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af83de926c81909e45160f9fc78799 |
completed | March 10, 2026, 2:37 a.m. |
Created at: March 6, 2026, 9:49 p.m.