Triple
T16274758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houyet |
E395094
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Dinant |
E587058
|
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: Dinant | Statement: [Houyet, borderedBy, Dinant]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dinant Context triple: [Houyet, borderedBy, Dinant]
-
A.
Dinant
chosen
Dinant is a picturesque Belgian town in Wallonia known for its dramatic cliffs along the Meuse River, its citadel, and as the birthplace of saxophone inventor Adolphe Sax.
-
B.
Debourg
Debourg is a tram terminus and transport hub in Lyon, France, serving as one end of the city’s T1 tram line.
-
C.
Couvin
Couvin is a municipality in southern Belgium known for its extensive forests, caves, and rural landscapes within the Walloon region.
-
D.
Comines
Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
-
E.
Souain
Souain is a commune in the Marne department of northeastern France, known for its World War I battlefields and memorials.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460c2d948190813b66e539a64a70 |
completed | April 17, 2026, 2:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0017c0ef4c8190b44ac84f71b2ed41 |
completed | May 10, 2026, 5:29 a.m. |
Created at: April 10, 2026, 5:05 a.m.