Triple

T9048527
Position Surface form Disambiguated ID Type / Status
Subject ANA Holdings Inc. E216821 entity
Predicate owns P347 FINISHED
Object ANA Wings E216824 NE 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: ANA Wings | Statement: [ANA Holdings Inc., owns, ANA Wings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ANA Wings
Context triple: [ANA Holdings Inc., owns, ANA Wings]
  • A. ANA Wings chosen
    ANA Wings is a Japanese regional airline operating domestic feeder and short-haul services on behalf of All Nippon Airways.
  • B. Wing
    Wing is an Alphabet Inc. subsidiary focused on developing and operating drone-based delivery services and related logistics technologies.
  • C. Wing
    Wing is an experimental mobile operating system and user interface project developed by X (formerly Google X) to explore new paradigms in smartphone interaction and design.
  • D. Albawings
    Albawings is an Albanian low-cost airline based in Tirana that operates short-haul passenger flights, primarily connecting Albania with destinations in Europe.
  • E. WINGO
    WINGO is the radio callsign used by Wingo, a low-cost Colombian airline operating domestic and international flights in Latin America.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6b51aa708190a37feecfd8deed2f completed April 1, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfebc0fd648190b0dd6cf62605b98f completed April 3, 2026, 4:33 p.m.
Created at: March 30, 2026, 7:09 p.m.