Triple
T29604425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valery Chkalov |
E754536
|
entity |
| Predicate | testedAircraftAtDeath |
P21445
|
FINISHED |
| Object | Polikarpov I-180 prototype |
—
|
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: Polikarpov I-180 prototype | Statement: [Valery Chkalov, testedAircraftAtDeath, Polikarpov I-180 prototype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedAircraftAtDeath Context triple: [Valery Chkalov, testedAircraftAtDeath, Polikarpov I-180 prototype]
-
A.
notableAircraftTested
Indicates that the subject conducted tests or evaluations on the specified aircraft, which is considered notable or significant.
-
B.
aircraftInvolvedInDeath
chosen
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
C.
testedAircraftOfManufacturer
Indicates that an entity (typically a person or organization) has performed testing on an aircraft produced by a specified manufacturer.
-
D.
aircraftFlown
Indicates that an entity (typically a person or organization) operates or pilots a particular aircraft.
-
E.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de5e2b88190bd2529cc77629609 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:24 p.m.