Triple
T10823134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-34 Choctaw |
E255423
|
entity |
| Predicate | tailRotorLocation |
P82738
|
FINISHED |
| Object | starboard side of tail |
—
|
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: starboard side of tail | Statement: [H-34 Choctaw, tailRotorLocation, starboard side of tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailRotorLocation Context triple: [H-34 Choctaw, tailRotorLocation, starboard side of tail]
-
A.
tailRotorPosition
chosen
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.
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.
-
D.
helipadLocation
Indicates the specific place or area where a helipad is situated or located.
-
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344c551c8190a7491d468b8a4a04 |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.