Triple

T9284404
Position Surface form Disambiguated ID Type / Status
Subject AmericanConnection E223150 entity
Predicate callsignUsed P1565 FINISHED
Object various callsigns of operating carriers — 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: various callsigns of operating carriers | Statement: [AmericanConnection, callsignUsed, various callsigns of operating carriers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: callsignUsed
Context triple: [AmericanConnection, callsignUsed, various callsigns of operating carriers]
  • A. callsign chosen
    Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
  • B. callsignCondition
    Indicates a condition or constraint that must be satisfied by an entity’s callsign within the relationship or context.
  • C. relatedCallsignUsage
    Indicates that one callsign is used in connection with, or as a variant of, another callsign in operational or identification contexts.
  • D. callsignOfOperator
    Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
  • E. callsignSeries
    Indicates that one entity is a member or installment within a series or sequence that shares the same callsign.
  • 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_69ca842123588190b3f2e1a69037d141 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd081e72988190917f425e64631837 completed April 1, 2026, 11:57 a.m.
PD Predicate disambiguation batch_69cc7a576ec88190bbb787eb82e2e539 completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:34 p.m.