Triple
T36846866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NR16020 |
E910571
|
entity |
| Predicate | firstFlightPurpose |
P79244
|
FINISHED |
| Object | preparation for world flight |
—
|
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: preparation for world flight | Statement: [NR16020, firstFlightPurpose, preparation for world flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightPurpose Context triple: [NR16020, firstFlightPurpose, preparation for world flight]
-
A.
firstFlightUse
Indicates that an entity is being used or operated for the very first time in a flight.
-
B.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
C.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
D.
flightPurpose
chosen
Indicates the reason or intended purpose for which a particular flight is being taken or operated.
-
E.
firstFlightFrom
Indicates that one entity is the earliest (chronologically first) flight departing from a given origin or on a given route among a set of flights.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.