Triple

T17943212
Position Surface form Disambiguated ID Type / Status
Subject SU95 E448635 entity
Predicate aircraftPrimaryMissionProfile P2860 FINISHED
Object regional scheduled airline service 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: regional scheduled airline service | Statement: [SU95, aircraftPrimaryMissionProfile, regional scheduled airline service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aircraftPrimaryMissionProfile
Context triple: [SU95, aircraftPrimaryMissionProfile, regional scheduled airline service]
  • A. primaryAircraftRole chosen
    Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
  • B. aircraftRoleSpecialization
    Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
  • C. basedAircraftRole
    Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
  • D. aircraftSecondaryMission
    Indicates the secondary mission or role that an aircraft is intended or configured to perform in addition to its primary mission.
  • E. aircraftCapability
    Indicates that an aircraft possesses a particular capability, function, or operational feature.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad97611c8190a861467ae51f6c48 completed April 19, 2026, 10:25 a.m.
PD Predicate disambiguation batch_69e3f8f2bd088190b1e22ad4d9cc8b13 completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:21 a.m.