Triple
T9695024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N612UA |
E234625
|
entity |
| Predicate | dateOfNotableFlight |
P89674
|
FINISHED |
| Object | 2001-09-11 |
—
|
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: 2001-09-11 | Statement: [N612UA, dateOfNotableFlight, 2001-09-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfNotableFlight Context triple: [N612UA, dateOfNotableFlight, 2001-09-11]
-
A.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
-
B.
firstFlightLandingDate
Indicates the calendar date on which an aircraft or flight successfully completed its first landing.
-
C.
associatedWithAviationMilestone
Indicates a relationship in which something is connected to, involved in, or plays a role in a significant event or achievement in the history or development of aviation.
-
D.
firstFlownAt
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
-
E.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d366c488190bc153c68fef197c2 |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b9e93c8190947cce56a3925364 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.