Triple
T30505352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Extension |
E776253
|
entity |
| Predicate | openedAsTurnpikeSegment |
P170361
|
FINISHED |
| Object | mid-20th century |
—
|
LITERAL 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: mid-20th century | Statement: [Northeast Extension, openedAsTurnpikeSegment, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTurnpikeSegment Context triple: [Northeast Extension, openedAsTurnpikeSegment, mid-20th century]
-
A.
openedAsTurnpike
chosen
Indicates that something was initially established or began operation as a toll road or turnpike.
-
B.
openedAsExpresswaySection
Indicates that a particular section of roadway was inaugurated and began operation specifically as an expressway segment.
-
C.
openedTollSection
Indicates that a toll road segment has been made available for use and is now open to traffic.
-
D.
openedSegmentBySegment
Indicates that something was opened gradually in distinct parts or stages, rather than all at once.
-
E.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 8:15 p.m.