Triple
T8072378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 16 |
E188404
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 16
SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
|
E715539
|
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 16 | Statement: [Maine State Route 16, abbreviation, SR 16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 16 Context triple: [Maine State Route 16, abbreviation, SR 16]
-
A.
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.
-
B.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
C.
SR 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
-
D.
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.
-
E.
SR 116
SR 116 is a state highway in Georgia that serves as an east–west transportation route connecting several communities in the west-central part of 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 16 Triple: [Maine State Route 16, abbreviation, SR 16]
Generated description
SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 16 Target entity description: SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
-
A.
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.
-
B.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
C.
SR 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
-
D.
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.
-
E.
SR 116
SR 116 is a state highway in Georgia that serves as an east–west transportation route connecting several communities in the west-central part of 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40482200819086c639f64c01fbb5 |
completed | March 31, 2026, 3:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbe67d9dc8190ad72e3f5ce7478e3 |
completed | April 1, 2026, 6:42 a.m. |
| NEDg | Description generation | batch_69ccc30f1fc48190991e0caa9ea6e735 |
completed | April 1, 2026, 7:02 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ccd7eca618819081e0c5452c8b1960 |
completed | April 1, 2026, 8:31 a.m. |
Created at: March 30, 2026, 5:27 p.m.