Triple

T20632072
Position Surface form Disambiguated ID Type / Status
Subject Lightning T.4 E506978 entity
Predicate originAircraftRole P2860 FINISHED
Object supersonic interceptor 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: supersonic interceptor | Statement: [Lightning T.4, originAircraftRole, supersonic interceptor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originAircraftRole
Context triple: [Lightning T.4, originAircraftRole, supersonic interceptor]
  • A. referredAircraftRole
    Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
  • B. basedAircraftRole
    Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
  • C. primaryAircraftRole chosen
    Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
  • D. carriedAircraftRole
    Indicates the functional role or mission type that an aircraft serves when it is carried by another platform (such as a ship or larger aircraft).
  • E. usedOnAircraftRole
    Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6ad0bdcd88190a59d68e03370b271 completed April 20, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69e5a0155bd48190b3c769a12cc2c83d completed April 20, 2026, 3:40 a.m.
Created at: April 16, 2026, 11:42 a.m.