Triple
T6669158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 178 |
E151680
|
entity |
| Predicate | flightTesting |
P72369
|
FINISHED |
| Object | conducted by Heinkel test pilots |
—
|
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: conducted by Heinkel test pilots | Statement: [Heinkel He 178, flightTesting, conducted by Heinkel test pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightTesting Context triple: [Heinkel He 178, flightTesting, conducted by Heinkel test pilots]
-
A.
notableAircraftTested
Indicates that the subject conducted tests or evaluations on the specified aircraft, which is considered notable or significant.
-
B.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
flyByWire
Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
-
E.
hasFixedWingTrainingRole
Indicates that an entity serves in a training capacity specifically related to the operation or use of fixed-wing aircraft.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6ce72809c8190be85f6e42ca1c8ea |
completed | March 27, 2026, 6:37 p.m. |
Created at: March 27, 2026, 2:02 p.m.