Triple
T13335616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 175 |
E317683
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | Maine State Route 172 |
E315015
|
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: Maine State Route 172 | Statement: [Maine State Route 175, hasJunctionWith, Maine State Route 172]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maine State Route 172 Context triple: [Maine State Route 175, hasJunctionWith, Maine State Route 172]
-
A.
Maine State Route 172
chosen
Maine State Route 172 is a state highway in Maine that connects the towns of Ellsworth and Blue Hill in Hancock County.
-
B.
Maine State Route 171
Maine State Route 171 is a state highway in Maine that serves as a local connector route within the state’s numbered highway network.
-
C.
Maine State Route 170
Maine State Route 170 is a state highway in Maine that serves as a regional connector for local communities within the state’s road network.
-
D.
Maine State Route 173
Maine State Route 173 is a state highway in Maine that connects several communities in the coastal region of the state.
-
E.
Maine State Route 177
Maine State Route 177 is a state highway in Maine that serves as a regional connector road within the state's numbered route network.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cff44e08190b9583baf0b626e42 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f730641f588190886119506e6dde8f |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:30 p.m.