Triple
T750106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 177 |
E15427
|
entity |
| Predicate | propellers |
P17498
|
FINISHED |
| Object | four-bladed propellers |
—
|
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: four-bladed propellers | Statement: [Heinkel He 177, propellers, four-bladed propellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellers Context triple: [Heinkel He 177, propellers, four-bladed propellers]
-
A.
propellerType
chosen
Indicates the specific kind or classification of propeller associated with an entity.
-
B.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
C.
propulsionCycle
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
-
D.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
E.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.