Triple

T16699966
Position Surface form Disambiguated ID Type / Status
Subject Treves E405818 entity
Predicate GermanName P6492 FINISHED
Object Trier E93600 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: Trier | Statement: [Treves, GermanName, Trier]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trier
Context triple: [Treves, GermanName, Trier]
  • A. Trier chosen
    Trier is a historic city in western Germany, renowned as one of the country’s oldest cities with extensive Roman ruins and medieval landmarks.
  • B. Speyer
    Speyer is a historic city in southwestern Germany on the Rhine River, renowned for its Romanesque imperial cathedral, a UNESCO World Heritage Site.
  • C. Aachen
    Aachen is a historic German city near the borders with Belgium and the Netherlands, renowned for its medieval cathedral, role as a coronation site for Holy Roman Emperors, and significance in both World Wars.
  • D. Mainz
    Mainz is a historic German city on the Rhine River known as a major ecclesiastical and political center of the Holy Roman Empire and today as the capital of the state of Rhineland-Palatinate.
  • E. Colmar
    Colmar is a picturesque historic town in northeastern France’s Alsace region, renowned for its well-preserved medieval and early Renaissance architecture and canals.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e383300d108190911e3cba8e07f2dd completed April 18, 2026, 1:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00aaed833c8190ab8a724d279dc52d completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:19 a.m.