Triple
T36438072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky VS-300 |
E897644
|
entity |
| Predicate | tailRotorBladesCount |
P185501
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Sikorsky VS-300, tailRotorBladesCount, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailRotorBladesCount Context triple: [Sikorsky VS-300, tailRotorBladesCount, 2]
-
A.
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.
-
B.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
-
C.
numberOfBladesMainRotor
Indicates the quantity of blades present on the main rotor in the relationship or system being described.
-
D.
numberOfPropellers
Indicates the quantity of propellers that an entity possesses or uses.
-
E.
propellerBladesPerPropeller
Indicates the number of blades associated with each individual propeller.
- F. None of above. chosen
Provenance (4 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.