Triple
T4795480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 3 |
E106700
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
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.
|
E470467
|
NE FINISHED |
How this triple was built (4 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 3 | Statement: [Alabama State Route 3, abbreviation, SR 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 3 Context triple: [Alabama State Route 3, abbreviation, SR 3]
-
A.
SR 316
SR 316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
B.
SR 2
SR 2 is a state highway in the Florida Panhandle that runs near the Alabama border, serving as an east–west route through rural communities.
-
C.
SR 13
SR 13 is a north–south state highway in Ohio that runs between the city of Mansfield and the village of Huron, passing through several counties in the north-central part of the state.
-
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 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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 3 Triple: [Alabama State Route 3, abbreviation, SR 3]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 3 Target entity description: 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.
-
A.
SR 316
SR 316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
B.
SR 2
SR 2 is a state highway in the Florida Panhandle that runs near the Alabama border, serving as an east–west route through rural communities.
-
C.
SR 13
SR 13 is a north–south state highway in Ohio that runs between the city of Mansfield and the village of Huron, passing through several counties in the north-central part of the state.
-
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 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.
- F. None of above. chosen
Provenance (5 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6609e9888190b49f99bb9fb2279d |
completed | March 20, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be43f512e0819086cc33009cd45c9a |
completed | March 21, 2026, 7:08 a.m. |
| NEDg | Description generation | batch_69be44cb99ac819089bbb941709a93c4 |
completed | March 21, 2026, 7:12 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69be451e8d7c81908d856e7966daa5fe |
completed | March 21, 2026, 7:13 a.m. |
Created at: March 20, 2026, 1:22 p.m.