Triple
T25494104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABX |
E638911
|
entity |
| Predicate | servesPassengerFlights |
P27830
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ABX, servesPassengerFlights, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPassengerFlights Context triple: [ABX, servesPassengerFlights, true]
-
A.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
-
B.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
-
C.
servesPassengerTrafficType
chosen
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
D.
operatesFeederFlightsFor
Indicates that one airline or carrier runs connecting or short-haul feeder flights on behalf of, or in support of, another airline’s main services.
-
E.
servesPassengerTrafficTo
Indicates that a transportation facility or service provides regular passenger traffic access or operations to a particular location or area.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 2:39 p.m.