Triple
T12977739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 176 |
E321572
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 176
SR 176 is a state highway in Maine that runs through Hancock County, connecting several coastal and inland communities.
|
E1017785
|
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 176 | Statement: [Maine State Route 176, abbreviation, SR 176]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 176 Context triple: [Maine State Route 176, abbreviation, SR 176]
-
A.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
B.
SR 17
SR 17 is a heavily traveled and winding state highway in California that connects San Jose in Silicon Valley with the city of Santa Cruz across the Santa Cruz Mountains.
-
C.
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.
-
D.
SR 16
SR 16 is a primary state highway in Washington that connects the Tacoma area to the Kitsap Peninsula, including the Tacoma Narrows Bridge crossing.
-
E.
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.
- 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 176 Triple: [Maine State Route 176, abbreviation, SR 176]
Generated description
SR 176 is a state highway in Maine that runs through Hancock County, connecting several coastal and inland communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 176 Target entity description: SR 176 is a state highway in Maine that runs through Hancock County, connecting several coastal and inland communities.
-
A.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
B.
SR 17
SR 17 is a heavily traveled and winding state highway in California that connects San Jose in Silicon Valley with the city of Santa Cruz across the Santa Cruz Mountains.
-
C.
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.
-
D.
SR 16
SR 16 is a primary state highway in Washington that connects the Tacoma area to the Kitsap Peninsula, including the Tacoma Narrows Bridge crossing.
-
E.
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.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbc277c881909ae77e8a44e06986 |
completed | May 3, 2026, 4:14 a.m. |
| NEDg | Description generation | batch_69f6cea882d48190add88a8463f7d544 |
completed | May 3, 2026, 4:27 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f6cf72a0cc8190bf8b6d606b8d0987 |
completed | May 3, 2026, 4:30 a.m. |
Created at: April 9, 2026, 8:38 p.m.