Triple
T20484843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBB Bo 115 |
E502561
|
entity |
| Predicate | hasTailRotor |
P96721
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MBB Bo 115, hasTailRotor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTailRotor Context triple: [MBB Bo 115, hasTailRotor, yes]
-
A.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
-
B.
tailRotorBlades
Indicates the relationship in which an entity functions as the rotor blades located at the tail of a rotorcraft, used for stability and directional control.
-
C.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
D.
hasPropeller
chosen
Indicates that an entity is equipped with or possesses a propeller as a functional component.
-
E.
rotorType
Indicates the specific kind or category of rotor associated with an entity.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b59ae2c8190bfa26a3f1e59b8d1 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.