Triple

T18761613
Position Surface form Disambiguated ID Type / Status
Subject Hanjin Group E458781 entity
Predicate owns P347 FINISHED
Object Jin Air NE NERFINISHED

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: Jin Air | Statement: [Hanjin Group, owns, Jin Air]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jin Air
Context triple: [Hanjin Group, owns, Jin Air]
  • A. Jin Air chosen
    Jin Air is a South Korean low-cost airline that operates domestic and international passenger flights.
  • B. Jeju Air
    Jeju Air is a South Korean low-cost airline that operates extensive domestic and international routes, particularly serving leisure and regional markets in East Asia.
  • C. Asiana Airlines
    Asiana Airlines is a major South Korean international airline based in Seoul, operating an extensive network of passenger and cargo services across Asia, Europe, North America, and Oceania.
  • D. Korean Air
    Korean Air is South Korea’s largest airline and flag carrier, operating extensive international and domestic passenger and cargo services worldwide.
  • E. Asia Pacific Airlines
    Asia Pacific Airlines is a cargo and charter airline based in Guam that primarily serves destinations across Micronesia and the Western Pacific region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e58d7fd5008190823bc7e37fdd6669 completed April 20, 2026, 2:20 a.m.
Created at: April 10, 2026, 11:52 a.m.