Triple

T7038102
Position Surface form Disambiguated ID Type / Status
Subject Geul E163435 entity
Predicate near P350 FINISHED
Object Maastricht E168527 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: Maastricht | Statement: [Geul, near, Maastricht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maastricht
Context triple: [Geul, near, Maastricht]
  • A. Maastricht chosen
    Maastricht is a historic city in the southeastern Netherlands known for its medieval architecture, vibrant cultural scene, and as the birthplace of the Maastricht Treaty that founded the European Union.
  • B. Bruges
    Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
  • 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. Hasselt
    Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
  • E. Hasselt
    Hasselt is a city in northeastern Belgium that serves as the capital of the province of Limburg in the Flemish region.
  • 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_69c6885e7c1c8190be32a8f79ab4e0cf completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e223077c819097992089fa83c563 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf7363b88190a082915ebac4f575 completed March 28, 2026, 11:45 a.m.
Created at: March 27, 2026, 2:36 p.m.