Triple
T16663151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison AE 2100A |
E404910
|
entity |
| Predicate | propellerSystem |
P17498
|
FINISHED |
| Object | Dowty R391 propeller compatible |
—
|
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: Dowty R391 propeller compatible | Statement: [Allison AE 2100A, propellerSystem, Dowty R391 propeller compatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellerSystem Context triple: [Allison AE 2100A, propellerSystem, Dowty R391 propeller compatible]
-
A.
propellerType
chosen
Indicates the specific kind or classification of propeller associated with an entity.
-
B.
propellerBlades
Indicates that something has propeller blades as a component or feature.
-
C.
propellerPosition
Indicates the spatial placement or mounting location of a propeller relative to the object it is attached to.
-
D.
propellerBladesPerPropeller
Indicates the number of blades associated with each individual propeller.
-
E.
hasPropeller
Indicates that an entity is equipped with or possesses a propeller as a functional component.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9afd048190b73bbc9c423915ca |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.