Triple
T26772871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaulding Turnpike |
E670028
|
entity |
| Predicate | openedAsTurnpike |
P170361
|
FINISHED |
| Object | 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: 20th century | Statement: [Spaulding Turnpike, openedAsTurnpike, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTurnpike Context triple: [Spaulding Turnpike, openedAsTurnpike, 20th century]
-
A.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
-
B.
openedTollSection
Indicates that a toll road segment has been made available for use and is now open to traffic.
-
C.
openedAsTerminus
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
D.
openedAsMotorway
Indicates that a road segment was initially opened to traffic specifically as a motorway.
-
E.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
- F. None of above. chosen
Provenance (4 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 4:03 a.m.