Triple

T21535090
Position Surface form Disambiguated ID Type / Status
Subject FEDRO E531329 entity
Predicate abbreviation P43 FINISHED
Object FEDRO E531329 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: FEDRO | Statement: [FEDRO, abbreviation, FEDRO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FEDRO
Context triple: [FEDRO, abbreviation, FEDRO]
  • A. FEDRO chosen
    FEDRO is the Swiss federal authority responsible for planning, constructing, operating, and maintaining the national road network.
  • B. Feder
    Feder is a German surname most notably associated with Gottfried Feder, an early economic theorist of the Nazi Party.
  • C. Federko
    Federko is the surname of Bernie Federko, a Canadian former professional ice hockey center and Hockey Hall of Famer best known for his career with the St. Louis Blues.
  • D. Fudam
    Fudam is a coastal village in the Diu district of the Indian union territory of Dadra and Nagar Haveli and Daman and Diu, known for its fishing community and proximity to Diu town.
  • E. FED
    FED is the commonly used abbreviation for the Faculty of Engineering and Design, an academic unit focused on engineering and design education and research.
  • 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_69e0c45e5b8881908ac18fc2f493b114 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee9d0ce8d08190b3233d7117a9b1ca completed April 26, 2026, 11:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a09e8339c04819092968f7a7baba3f8 completed May 17, 2026, 4:09 p.m.
Created at: April 16, 2026, 6:27 p.m.