Triple
T34124645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soloviev D-30F6 |
E875240
|
entity |
| Predicate | firstFlightPlatform |
P205330
|
FINISHED |
| Object | MiG-31 prototype |
—
|
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: MiG-31 prototype | Statement: [Soloviev D-30F6, firstFlightPlatform, MiG-31 prototype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightPlatform Context triple: [Soloviev D-30F6, firstFlightPlatform, MiG-31 prototype]
-
A.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
B.
firstFlightProgram
Indicates that the subject entity is the first flight program associated with the object entity (such as an aircraft, spacecraft, or mission).
-
C.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
D.
firstFlightService
Indicates that an entity operates or provides service on the earliest scheduled flight in a given context or route.
-
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. 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:53 a.m.