Triple
T15968338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgloon |
E387254
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Heers |
E537814
|
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: Heers | Statement: [Borgloon, borderedBy, Heers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heers Context triple: [Borgloon, borderedBy, Heers]
-
A.
Heers
chosen
Heers is a rural municipality in the Belgian province of Limburg, known for its agricultural landscape and historic villages.
-
B.
Sterksel
Sterksel is a small village in the Dutch province of North Brabant, known for its rural character and location within the municipality of Heeze-Leende.
-
C.
Hoornaar
Hoornaar is a village in the Dutch province of South Holland, known for its rural character and traditional polder landscape.
-
D.
Heezen
Heezen is a surname most notably associated with American geologist and oceanographer Bruce C. Heezen, a pioneer in mapping the ocean floor.
-
E.
Scherpenzeel
Scherpenzeel is a small Dutch municipality in the province of Gelderland, known for its rural character and historic village center.
- 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_69ffbe87149081909ac6129126f597c2 |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:54 a.m.