Triple
T8923348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Allegheny Passage |
E212477
|
entity |
| Predicate | trailDesignation |
P86425
|
FINISHED |
| Object | rail-trail |
—
|
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: rail-trail | Statement: [Great Allegheny Passage, trailDesignation, rail-trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDesignation Context triple: [Great Allegheny Passage, trailDesignation, rail-trail]
-
A.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
B.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
C.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
D.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
-
E.
lineDesignationIntroducedBy
Indicates that a particular line designation was introduced or established by a specific agent or source.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6652d63881908821c8735984322a |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.