Triple
T35098752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY 23 |
E1012941
|
entity |
| Predicate | connectsToAtEastTerminus |
P167776
|
FINISHED |
| Object | Massachusetts Route 23 |
—
|
NE NERFINISHED |
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: Massachusetts Route 23 | Statement: [NY 23, connectsToAtEastTerminus, Massachusetts Route 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToAtEastTerminus Context triple: [NY 23, connectsToAtEastTerminus, Massachusetts Route 23]
-
A.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
easternTerminusNearby
Indicates that the eastern endpoint of one entity is located close to the referenced entity.
-
D.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
E.
terminusConnectsTo
chosen
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
- F. None of above.
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:01 p.m.