Triple

T1736187
Position Surface form Disambiguated ID Type / Status
Subject XPG E37923 entity
Predicate relatedTo P37 FINISHED
Object ORY E10907 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: ORY | Statement: [XPG, relatedTo, ORY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ORY
Context triple: [XPG, relatedTo, ORY]
  • A. ORY chosen
    ORY is the three-letter IATA airport code for Paris Orly Airport, a major international airport serving the Paris metropolitan area in France.
  • B. OR
    OR is the official two-letter United States Postal Service abbreviation for the state of Oregon.
  • C. URY
    URY is the three-letter ISO 3166-1 alpha-3 country code assigned to Uruguay.
  • D. TOR
    TOR is the standard three-letter abbreviation used to represent the Toronto Maple Leafs in sports standings, statistics, and media.
  • E. WR
    WR is the abbreviation for the German Council of Science and Humanities, a key advisory body that counsels the German federal and state governments on science, research, and higher education policy.
  • 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_69a8861cc6ac8190ac0b2e31ccf62851 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa63a369048190bae352573f5082f1 completed March 6, 2026, 5:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad8b008b7881909ac568af010bcf99 completed March 8, 2026, 2:43 p.m.
Created at: March 4, 2026, 7:30 p.m.