Triple

T10359391
Position Surface form Disambiguated ID Type / Status
Subject Aérospatiale SA 321 Super Frelon E244092 entity
Predicate helicopterConfiguration P3541 FINISHED
Object single main rotor with tail 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 with tail rotor | Statement: [Aérospatiale SA 321 Super Frelon, helicopterConfiguration, single main rotor with tail rotor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: helicopterConfiguration
Context triple: [Aérospatiale SA 321 Super Frelon, helicopterConfiguration, single main rotor with tail rotor]
  • A. tailRotorConfiguration
    Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
  • B. isHelicopterOf
    Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
  • C. aircraftConfiguration chosen
    Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
  • D. helicopterMass
    Indicates the mass associated with a helicopter.
  • E. isHelicopterOnly
    Indicates that the subject is restricted to or designated exclusively for use by helicopters.
  • 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_69d381b22b8c8190aaed476be5f872a9 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e95708c481909c8c8cb2a57bf6d6 completed April 7, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69d4dfa657f481909cc5cc8fec00ad19 completed April 7, 2026, 10:42 a.m.
Created at: April 6, 2026, 11:59 a.m.