Triple
T33659839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B712 |
E862320
|
entity |
| Predicate | aircraftLineage |
P17727
|
FINISHED |
| Object | McDonnell Douglas MD-95 |
—
|
NE NERFINISHED |
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: McDonnell Douglas MD-95 | Statement: [B712, aircraftLineage, McDonnell Douglas MD-95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftLineage Context triple: [B712, aircraftLineage, McDonnell Douglas MD-95]
-
A.
notableAircraftFamily
Indicates that one entity is a well-known or historically significant family or series of aircraft associated with the other entity.
-
B.
formerAircraft
Indicates that an entity was previously used or designated as an aircraft but no longer holds that status.
-
C.
aircraftGeneration
chosen
Indicates a generational relationship between aircraft, such as one model being a successor, predecessor, or belonging to a specific generation relative to another.
-
D.
subjectAircraftNotableVariant
Indicates that the subject aircraft has a notable or significant variant related to it.
-
E.
aircraftIntroducedOfAircraft
Indicates that a specific aircraft model was introduced or entered service on a particular date or in a particular time period.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:42 a.m.