Triple
T1952657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FlyAway |
E42192
|
entity |
| Predicate | arrivalLocationType |
P33480
|
FINISHED |
| Object | park‑and‑ride facilities |
—
|
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: park‑and‑ride facilities | Statement: [FlyAway, arrivalLocationType, park‑and‑ride facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalLocationType Context triple: [FlyAway, arrivalLocationType, park‑and‑ride facilities]
-
A.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
B.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
C.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
D.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
E.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3501d108190bc5cb23f53db4411 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1ddccbc8190bf2bd8bac673c0c5 |
completed | March 7, 2026, 5:04 a.m. |
Created at: March 4, 2026, 7:36 p.m.