Triple

T7153025
Position Surface form Disambiguated ID Type / Status
Subject British Overseas Airways Corporation E166738 entity
Predicate notableRoute P22 FINISHED
Object London–Tokyo
London–Tokyo is a major intercontinental air route linking the capital cities of the United Kingdom and Japan.
 E644848 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: London–Tokyo | Statement: [British Overseas Airways Corporation, notableRoute, London–Tokyo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: London–Tokyo
Context triple: [British Overseas Airways Corporation, notableRoute, London–Tokyo]
  • A. Seoul–Tokyo
    Seoul–Tokyo is a major international air route connecting the capitals of South Korea and Japan, serving as a key corridor for business and tourism between the two countries.
  • B. Seoul–London
    Seoul–London is an intercontinental air route connecting the capital cities of South Korea and the United Kingdom.
  • C. Moscow–Tokyo
    Moscow–Tokyo refers to the long-haul international air route connecting the capitals of Russia and Japan.
  • D. Tokyo
    Tokyo is Japan’s largest metropolis and a global center of finance, culture, technology, and transportation.
  • E. New York–London
    New York–London is a major transatlantic air route connecting the United States and the United Kingdom, historically served by numerous international carriers.
  • 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: London–Tokyo
Triple: [British Overseas Airways Corporation, notableRoute, London–Tokyo]
Generated description
London–Tokyo is a major intercontinental air route linking the capital cities of the United Kingdom and Japan.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: London–Tokyo
Target entity description: London–Tokyo is a major intercontinental air route linking the capital cities of the United Kingdom and Japan.
  • A. Seoul–Tokyo
    Seoul–Tokyo is a major international air route connecting the capitals of South Korea and Japan, serving as a key corridor for business and tourism between the two countries.
  • B. Seoul–London
    Seoul–London is an intercontinental air route connecting the capital cities of South Korea and the United Kingdom.
  • C. Moscow–Tokyo
    Moscow–Tokyo refers to the long-haul international air route connecting the capitals of Russia and Japan.
  • D. Tokyo
    Tokyo is Japan’s largest metropolis and a global center of finance, culture, technology, and transportation.
  • E. New York–London
    New York–London is a major transatlantic air route connecting the United States and the United Kingdom, historically served by numerous international carriers.
  • 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_69c68886779c8190a8e3fbabffe68253 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e7f52c1081908c4fa424d5e965bc completed March 27, 2026, 8:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7adb0ea288190b7eef76de30a3a1e completed March 28, 2026, 10:30 a.m.
NEDg Description generation batch_69c7ae1bde448190b546d292d213c8c9 completed March 28, 2026, 10:31 a.m.
NED2 Entity disambiguation (via description) batch_69c7ae73e1a88190a18488b3155b2542 completed March 28, 2026, 10:33 a.m.
Created at: March 27, 2026, 2:46 p.m.