Triple
T22207204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tervuren |
E548842
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Kortenberg |
—
|
NE NERFINISHED |
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: Kortenberg | Statement: [Tervuren, nearbyCity, Kortenberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kortenberg Context triple: [Tervuren, nearbyCity, Kortenberg]
-
A.
Kortenberg
chosen
Kortenberg is a municipality in the Flemish Brabant province of Belgium, located between Brussels and Leuven and known for its residential character and green surroundings.
-
B.
Kortenaken
Kortenaken is a rural municipality in the Flemish Brabant province of Belgium, known for its agricultural landscape and small village communities.
-
C.
Koppenberg
The Koppenberg is a short but brutally steep cobbled hill in the Flemish Ardennes, famed as one of the most iconic and decisive climbs in professional cycling.
-
D.
Zandbergen
Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
-
E.
Zandbergen
Zandbergen is a small hamlet in the municipality of Losser in the province of Overijssel in the eastern Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2936a481909aa84c7983ed49ee |
completed | April 28, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:36 p.m.