Triple
T14039961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 100 (Georgia) |
E337817
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | SR 1 (Georgia) |
E124044
|
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 1 (Georgia) | Statement: [SR 100 (Georgia), hasJunctionWith, SR 1 (Georgia)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 1 (Georgia) Context triple: [SR 100 (Georgia), hasJunctionWith, SR 1 (Georgia)]
-
A.
SR 1
SR 1 is a designation for a Florida state highway route that forms part of the state's numbered road network.
-
B.
SR 1
chosen
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 11
SR 11 is a planned and partially completed state highway intended to serve as a transportation corridor within its state’s road network.
-
D.
SR 101
SR 101, commonly known as Loop 101, is a major beltway freeway serving the Phoenix metropolitan area in Arizona.
-
E.
SR 111
SR 111 is a state highway in Maine that runs east–west, connecting the city of Biddeford to the town of Alfred and serving as an important regional route in York County.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de30ee374081908b6b5e8f81dd90f2 |
completed | April 14, 2026, 12:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc33dbc8c819080b6cb3d589da7a1 |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:20 p.m.