Triple

T11534685
Position Surface form Disambiguated ID Type / Status
Subject Trois-Ponts E273515 entity
Predicate locatedNear P294 FINISHED
Object Stavelot E262737 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: Stavelot | Statement: [Trois-Ponts, locatedNear, Stavelot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stavelot
Context triple: [Trois-Ponts, locatedNear, Stavelot]
  • A. Stavelot chosen
    Stavelot is a historic town in the Ardennes region of Wallonia, Belgium, known for its former Benedictine abbey and traditional Laetare carnival.
  • B. Merode
    Merode is a key Brussels Metro station serving as an important interchange point near the Parc du Cinquantenaire in eastern Brussels.
  • C. Dendermonde
    Dendermonde is a historic city in East Flanders, Belgium, known for its medieval architecture and UNESCO-recognized Ros Beiaard procession.
  • D. Gembloux
    Gembloux is a town in the Walloon region of Belgium known for its historic center and agricultural university.
  • E. Moensberg
    Moensberg is a residential neighborhood in the municipality of Uccle in the Brussels-Capital Region of Belgium.
  • 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_69d6aae3fbec8190a14632a5df2538b6 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8839b4bb48190b748ec4119f36c11 completed April 10, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6858af0d081909078d5862ec3d469 completed April 20, 2026, 7:59 p.m.
Created at: April 8, 2026, 9:37 p.m.