Triple
T22503199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Flyer III |
E556325
|
entity |
| Predicate | hasPropellerConfiguration |
P17498
|
FINISHED |
| Object | twin pusher 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: twin pusher propellers | Statement: [Wright Flyer III, hasPropellerConfiguration, twin pusher propellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropellerConfiguration Context triple: [Wright Flyer III, hasPropellerConfiguration, twin pusher propellers]
-
A.
hasPropeller
Indicates that an entity is equipped with or possesses a propeller as a functional component.
-
B.
hasVariablePitchPropeller
Indicates that an entity is equipped with or uses a propeller whose blade pitch can be adjusted during operation.
-
C.
hasConstantSpeedPropeller
Indicates that an entity is equipped with or utilizes a propeller that operates at a constant rotational speed.
-
D.
propellerType
chosen
Indicates the specific kind or classification of propeller associated with an entity.
-
E.
hasWingConfiguration
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5a01888190ba65a05616b63cbe |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.