Triple
T26097381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairey Rotodyne |
E658308
|
entity |
| Predicate | rotorDriveForVTOL |
P89012
|
FINISHED |
| Object | tip-jet powered 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: tip-jet powered rotor | Statement: [Fairey Rotodyne, rotorDriveForVTOL, tip-jet powered rotor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorDriveForVTOL Context triple: [Fairey Rotodyne, rotorDriveForVTOL, tip-jet powered rotor]
-
A.
tailRotorPosition
Indicates the spatial location or mounting point of a vehicle’s tail rotor relative to the rest of the vehicle.
-
B.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
-
C.
rotorType
chosen
Indicates the specific kind or category of rotor associated with an entity.
-
D.
rotorConfiguration
Indicates the specific arrangement and setup of rotors within a rotor-based system or mechanism.
-
E.
thrustVectorControl
Indicates the capability to direct or adjust the direction of thrust from a propulsion system to control an object's attitude or trajectory.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607381a8c8190ad11235c85be02e1 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:52 p.m.