Triple

T4652245
Position Surface form Disambiguated ID Type / Status
Subject Trans World Airlines E102321 entity
Predicate notableRoute P22 FINISHED
Object New York–Paris E48096 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: New York–Paris | Statement: [Trans World Airlines, notableRoute, New York–Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: New York–Paris
Context triple: [Trans World Airlines, notableRoute, New York–Paris]
  • A. New York–Paris chosen
    New York–Paris is a major transatlantic air route connecting the United States and France, linking New York City with the French capital.
  • B. London–Paris
    London–Paris is a major international rail route connecting the capitals of the United Kingdom and France via the Channel Tunnel.
  • C. Paris–Amsterdam
    Paris–Amsterdam is a major international high-speed rail route linking the capitals of France and the Netherlands.
  • D. Paris–Basel
    Paris–Basel is an international air route linking the French capital Paris with the Swiss city of Basel.
  • E. Moscow–Paris
    Moscow–Paris is a major international air route linking the capitals of Russia and France.
  • 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_69bd43d71a308190afea7280841b0de8 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6314883481908f085a7af497b0d8 completed March 20, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfaeb1ee081909ef641953bdf8df3 completed March 21, 2026, 1:56 a.m.
Created at: March 20, 2026, 1:14 p.m.