Triple
T34439790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQ22 |
E884064
|
entity |
| Predicate | returnFlightNumber |
P188132
|
FINISHED |
| Object | SQ21 |
—
|
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: SQ21 | Statement: [SQ22, returnFlightNumber, SQ21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnFlightNumber Context triple: [SQ22, returnFlightNumber, SQ21]
-
A.
originatingFlight
Indicates that one entity is the original or initial flight from which another flight, journey, or related record derives or is associated.
-
B.
finalFlightNumber
Indicates the flight number assigned to the last or concluding segment of a journey or itinerary.
-
C.
vehicleFlightNumber
Indicates the specific flight number associated with a given vehicle (such as an aircraft) in an air transport context.
-
D.
secondFlightDate
Indicates the date on which an entity undertakes its second flight or airborne operation.
-
E.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 1, 2026, 2 a.m.