Triple
T20484842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBB Bo 115 |
E502561
|
entity |
| Predicate | hasRotorConfiguration |
P29958
|
FINISHED |
| Object | single main rotor |
—
|
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: single main rotor | Statement: [MBB Bo 115, hasRotorConfiguration, single main rotor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotorConfiguration Context triple: [MBB Bo 115, hasRotorConfiguration, single main rotor]
-
A.
rotorConfiguration
chosen
Indicates the specific arrangement and setup of rotors within a rotor-based system or mechanism.
-
B.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
C.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
D.
rotorType
Indicates the specific kind or category of rotor associated with an entity.
-
E.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
- 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.