Triple
T6494420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 11 |
E148119
|
entity |
| Predicate | hasRouteDesignation |
P5539
|
FINISHED |
| Object | SR 11 |
E286152
|
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 11 | Statement: [Georgia State Route 11, hasRouteDesignation, SR 11]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 11 Context triple: [Georgia State Route 11, hasRouteDesignation, SR 11]
-
A.
SR 11
chosen
SR 11 is a planned and partially completed state highway intended to serve as a transportation corridor within its state’s road network.
-
B.
SR 1
SR 1 is a major north–south state highway in Georgia that largely follows the route of U.S. Route 27 across the state.
-
C.
SR 18
SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
-
D.
SR 16
SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
-
E.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab7c0b8819091437a293b40dfd2 |
completed | March 22, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c653c21f948190989da451bc573b4d |
completed | March 27, 2026, 9:54 a.m. |
Created at: March 22, 2026, 4:53 p.m.