Triple
T4118298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Atlantic GlobalFlyer |
E90346
|
entity |
| Predicate | notableFlightEndDate |
P54379
|
FINISHED |
| Object | 2005-03-03 |
—
|
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: 2005-03-03 | Statement: [Virgin Atlantic GlobalFlyer, notableFlightEndDate, 2005-03-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFlightEndDate Context triple: [Virgin Atlantic GlobalFlyer, notableFlightEndDate, 2005-03-03]
-
A.
finalCommercialFlightDate
Indicates the calendar date on which an entity’s last commercial flight operation took place.
-
B.
lastShuttleFlightDate
Indicates the calendar date on which the most recent shuttle flight associated with the subject took place.
-
C.
lastCrewedLandingDate
Indicates the calendar date on which the most recent crewed landing associated with the subject took place.
-
D.
winningFlightDate
Indicates the date on which the associated flight is determined to be the winning or selected one among a set of candidate flights.
-
E.
lastCrewedFlightDate
Indicates the calendar date on which an aircraft, spacecraft, or similar vehicle was most recently operated with a human crew onboard.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.