Triple
T16476300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTH |
E400194
|
entity |
| Predicate | usedInJourneyPlanningSystems |
P41162
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PTH, usedInJourneyPlanningSystems, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInJourneyPlanningSystems Context triple: [PTH, usedInJourneyPlanningSystems, yes]
-
A.
usedForJourneyPlanning
chosen
Indicates that something is utilized to assist in planning or organizing a journey or trip.
-
B.
isUsedInTransportTimetables
Indicates that something is employed or referenced within transport timetables or schedules.
-
C.
usedByTransitSystem
Indicates that something is utilized or operated by a transit or public transportation system.
-
D.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
-
E.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd4f53081908f78b88435c8c719 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.