Triple

T16750170
Position Surface form Disambiguated ID Type / Status
Subject JAT Yugoslav Airlines E407051 entity
Predicate notableRoute P22 FINISHED
Object Belgrade–Toronto
Belgrade–Toronto was a long-haul intercontinental air route connecting the capital of former Yugoslavia with Canada, historically operated by JAT Yugoslav Airlines.
 E1232600 NE FINISHED

How this triple was built (4 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: Belgrade–Toronto | Statement: [JAT Yugoslav Airlines, notableRoute, Belgrade–Toronto]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Belgrade–Toronto
Context triple: [JAT Yugoslav Airlines, notableRoute, Belgrade–Toronto]
  • A. Moscow–Prague
    Moscow–Prague is an international air route connecting the capitals of Russia and the Czech Republic.
  • B. Moscow–Paris
    Moscow–Paris is a major international air route linking the capitals of Russia and France.
  • C. Vienna–Hamburg
    Vienna–Hamburg is an international overnight rail connection linking Austria’s capital with the major German port city of Hamburg.
  • D. Innsbruck–Hamburg
    Innsbruck–Hamburg is an overnight Nightjet rail connection linking the Austrian city of Innsbruck with the German port city of Hamburg.
  • E. Toronto Metros-Croatia
    Toronto Metros-Croatia was a professional soccer club based in Toronto that competed in the North American Soccer League during the 1970s.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Belgrade–Toronto
Triple: [JAT Yugoslav Airlines, notableRoute, Belgrade–Toronto]
Generated description
Belgrade–Toronto was a long-haul intercontinental air route connecting the capital of former Yugoslavia with Canada, historically operated by JAT Yugoslav Airlines.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Belgrade–Toronto
Target entity description: Belgrade–Toronto was a long-haul intercontinental air route connecting the capital of former Yugoslavia with Canada, historically operated by JAT Yugoslav Airlines.
  • A. Moscow–Prague
    Moscow–Prague is an international air route connecting the capitals of Russia and the Czech Republic.
  • B. Moscow–Paris
    Moscow–Paris is a major international air route linking the capitals of Russia and France.
  • C. Vienna–Hamburg
    Vienna–Hamburg is an international overnight rail connection linking Austria’s capital with the major German port city of Hamburg.
  • D. Innsbruck–Hamburg
    Innsbruck–Hamburg is an overnight Nightjet rail connection linking the Austrian city of Innsbruck with the German port city of Hamburg.
  • E. Toronto Metros-Croatia
    Toronto Metros-Croatia was a professional soccer club based in Toronto that competed in the North American Soccer League during the 1970s.
  • F. None of above. chosen

Provenance (5 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3aa265a908190a87fa4612bfe6396 completed April 18, 2026, 3:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a522255c8190ab16d7ad233fcd3b completed May 10, 2026, 3:32 p.m.
NEDg Description generation batch_6a00a6b2d7b08190841de0e849eac604 completed May 10, 2026, 3:39 p.m.
NED2 Entity disambiguation (via description) batch_6a00a761530481909b27b6844d2324f0 completed May 10, 2026, 3:42 p.m.
Created at: April 10, 2026, 5:21 a.m.