Triple
T7780379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia |
E221498
|
entity |
| Predicate | firstFlightStartDate |
P28082
|
FINISHED |
| Object | 1981-04-12 |
—
|
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: 1981-04-12 | Statement: [Columbia, firstFlightStartDate, 1981-04-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightStartDate Context triple: [Columbia, firstFlightStartDate, 1981-04-12]
-
A.
firstFlightPeriod
Indicates the time period during which an entity’s first flight or initial airborne operation took place.
-
B.
firstFlownAt
chosen
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
-
C.
firstFlightLandingDate
Indicates the calendar date on which an aircraft or flight successfully completed its first landing.
-
D.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
E.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:20 p.m.