Triple
T30171515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Allegheny Passage |
E766932
|
entity |
| Predicate | completedAsContinuousTrail |
P174301
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Great Allegheny Passage, completedAsContinuousTrail, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedAsContinuousTrail Context triple: [Great Allegheny Passage, completedAsContinuousTrail, 2013]
-
A.
completedAsContinuousRoute
Indicates that an activity or journey was carried out in one uninterrupted, continuous sequence without breaks or segmentation.
-
B.
completedAsContinuousMotorway
Indicates that a road segment has been fully built and functions as an unbroken, continuously drivable motorway.
-
C.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
D.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
E.
completedAlongside
Indicates that one action, task, or process was completed at the same time and in coordination with another.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 29, 2026, 7:24 p.m.