Triple

T15968404
Position Surface form Disambiguated ID Type / Status
Subject Looz E387256 entity
Predicate capital P234 FINISHED
Object Borgloon E387254 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: Borgloon | Statement: [Looz, capital, Borgloon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borgloon
Context triple: [Looz, capital, Borgloon]
  • A. Borgloon chosen
    Borgloon is a historic town in the Belgian province of Limburg that once served as the political and administrative center of the medieval County of Loon.
  • B. Borsele
    Borsele is a municipality in the Dutch province of Zeeland, known for its rural landscape, villages, and the nearby Borssele nuclear power plant.
  • C. Bredius
    Bredius is a Dutch surname most notably associated with Abraham Bredius, a prominent art historian and expert on Dutch Golden Age painting.
  • D. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • E. Borgnis
    Borgnis is a German-language surname most notably borne by August Ferdinand Julius Borgnis, a historical figure.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157277e7881908d49f4874766b3b5 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffe46d180c81909be66f628d1bdf72 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:54 a.m.