Triple
T9414950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 127 |
E226994
|
entity |
| Predicate | highwayDesignation |
P28856
|
FINISHED |
| Object |
SR 127
SR 127 is a state highway in Maine that connects several coastal communities and provides access to the Mid Coast region.
|
E797566
|
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 127 | Statement: [Maine State Route 127, highwayDesignation, SR 127]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 127 Context triple: [Maine State Route 127, highwayDesignation, SR 127]
-
A.
SR 127
SR 127 is a California state highway running through the Mojave Desert, providing a key route between Interstate 15 near Baker and the Nevada state line near Death Valley.
-
B.
SR 121
SR 121 is a state highway in California that runs through Sonoma and Napa counties, serving as a key route to the Napa Valley wine region.
-
C.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
D.
SR 117
SR 117 is a state highway in Maine that runs through several counties, connecting multiple rural towns and regional routes.
-
E.
SR 112
SR 112 is a state highway in Maine that serves as a regional connector route between several communities in the southern 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 127 Triple: [Maine State Route 127, highwayDesignation, SR 127]
Generated description
SR 127 is a state highway in Maine that connects several coastal communities and provides access to the Mid Coast region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 127 Target entity description: SR 127 is a state highway in Maine that connects several coastal communities and provides access to the Mid Coast region.
-
A.
SR 127
SR 127 is a California state highway running through the Mojave Desert, providing a key route between Interstate 15 near Baker and the Nevada state line near Death Valley.
-
B.
SR 121
SR 121 is a state highway in California that runs through Sonoma and Napa counties, serving as a key route to the Napa Valley wine region.
-
C.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
D.
SR 117
SR 117 is a state highway in Maine that runs through several counties, connecting multiple rural towns and regional routes.
-
E.
SR 112
SR 112 is a state highway in Maine that serves as a regional connector route between several communities in the southern 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c7bd648190b17f082883c98239 |
completed | April 1, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d107baad74819090a746c06feb28ac |
completed | April 4, 2026, 12:44 p.m. |
| NEDg | Description generation | batch_69d108466fb481909682fcaac354b312 |
completed | April 4, 2026, 12:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d108be82888190b0ec08119cd00b68 |
completed | April 4, 2026, 12:49 p.m. |
Created at: March 30, 2026, 7:47 p.m.