Triple
T7526227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 22 |
E177898
|
entity |
| Predicate | hasDepartureEnd |
P77333
|
FINISHED |
| Object | Runway 22 departure end |
—
|
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: Runway 22 departure end | Statement: [Runway 22, hasDepartureEnd, Runway 22 departure end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartureEnd Context triple: [Runway 22, hasDepartureEnd, Runway 22 departure end]
-
A.
hasDepartureSide
Indicates the side or direction from which an entity departs or leaves a location.
-
B.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
C.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
-
D.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
E.
endLocationOfJourney
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f555455c81908850210bcad96ac2 |
completed | March 27, 2026, 9:23 p.m. |
Created at: March 27, 2026, 3:46 p.m.