Triple
T12685134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-126 |
E303046
|
entity |
| Predicate | derivedFromCivilAircraft |
P89695
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tupolev Tu-126, derivedFromCivilAircraft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromCivilAircraft Context triple: [Tupolev Tu-126, derivedFromCivilAircraft, true]
-
A.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
B.
basedOnAircraft
chosen
Indicates that one entity is derived from, modeled after, or otherwise uses a particular aircraft as its basis or primary reference.
-
C.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
appliedToAircraftDesignedBy
Indicates that something (such as a component, system, or regulation) is applied to an aircraft that was designed by a specified designer or organization.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d7cd4c81909521839ef5859799 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.