Triple
T4208624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air France Flight 447 |
E93840
|
entity |
| Predicate | timeOfLossOfContactUTC |
P54757
|
FINISHED |
| Object | 2009-06-01 around 02:14 |
—
|
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: 2009-06-01 around 02:14 | Statement: [Air France Flight 447, timeOfLossOfContactUTC, 2009-06-01 around 02:14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfLossOfContactUTC Context triple: [Air France Flight 447, timeOfLossOfContactUTC, 2009-06-01 around 02:14]
-
A.
missionDurationToLastContact
Indicates the length of time from the mission’s start until the most recent (or final) communication contact.
-
B.
lastPrimaryRadarContactTimeLocal
Indicates the local-time timestamp when the most recent primary radar contact with the entity was recorded.
-
C.
landingTimeUTC
Indicates the exact time, expressed in Coordinated Universal Time (UTC), at which an entity (such as an aircraft or spacecraft) completes its landing.
-
D.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
-
E.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:03 p.m.