Triple

T8098768
Position Surface form Disambiguated ID Type / Status
Subject Dyle river basin E189052 entity
Predicate containsSettlement P847 FINISHED
Object Louvain (Leuven) E78057 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: Louvain (Leuven) | Statement: [Dyle river basin, containsSettlement, Louvain (Leuven)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Louvain (Leuven)
Context triple: [Dyle river basin, containsSettlement, Louvain (Leuven)]
  • A. Leuven chosen
    Leuven is a historic Belgian city known for hosting KU Leuven, one of Europe’s leading research universities, and for its vibrant academic and cultural life.
  • B. Ghent
    Ghent is a historic city in the Flemish region of Belgium, known for its medieval architecture, canals, and role as a major cultural and economic center in the Middle Ages.
  • C. Ghent
    Ghent is a small unincorporated community and ski-area destination located in Raleigh County, West Virginia, United States.
  • 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_69ca82b886d88190a9cba0d5a4a27521 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb42961ad4819085d023427fc5ac5f completed March 31, 2026, 3:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ccecf8f4a48190be0af148a9da4713 completed April 1, 2026, 10:01 a.m.
Created at: March 30, 2026, 5:30 p.m.