Triple

T1886950
Position Surface form Disambiguated ID Type / Status
Subject Intercités E39984 entity
Predicate distinguishedFrom P1612 FINISHED
Object TER E41185 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: TER | Statement: [Intercités, distinguishedFrom, TER]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TER
Context triple: [Intercités, distinguishedFrom, TER]
  • A. TER chosen
    TER is a network of regional express trains in France that provides local passenger rail services across various regions.
  • B. TR
    TR is the two-letter ISO 3166-1 alpha-2 country code assigned to Turkey for international standardization and referencing.
  • C. TOR
    TOR is the standard three-letter abbreviation used to represent the Toronto Maple Leafs in sports standings, statistics, and media.
  • D. TOR
    TOR is the official code designation used for the Georgian football club FC Torpedo Kutaisi.
  • E. tet
    tet is the ISO 639-1 language code for Tetum, an Austronesian language spoken primarily in East Timor.
  • 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_69a88633e4fc8190b7eb40463e048ec5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb121a3cc81909c60ac65627142d1 completed March 7, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69addf63863881908efd8010db14b8a8 completed March 8, 2026, 8:43 p.m.
Created at: March 4, 2026, 7:34 p.m.