Triple
T5792955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GA-316 |
E128438
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 316 |
E128436
|
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 316 | Statement: [GA-316, abbreviation, SR 316]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 316 Context triple: [GA-316, abbreviation, SR 316]
-
A.
SR 316
chosen
SR 316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
B.
SR 32
SR 32 is a major east–west state highway in Ohio that spans much of the southern part of the state, connecting Cincinnati to the Ohio River valley and Appalachian regions.
-
C.
SR 3
SR 3 is the internal designation for a major north–south state highway corridor in Alabama that largely follows the route of U.S. Route 31.
-
D.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
E.
SR 269
SR 269 is a short state highway in Florida that serves local traffic in the state's northern 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c09824c7f0819095565e0f29b3a508 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:51 p.m.