Triple
T14815856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esneux |
E348311
|
entity |
| Predicate | neighboringMunicipality |
P17964
|
FINISHED |
| Object | Aywaille |
E295671
|
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: Aywaille | Statement: [Esneux, neighboringMunicipality, Aywaille]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aywaille Context triple: [Esneux, neighboringMunicipality, Aywaille]
-
A.
Aywaille
chosen
Aywaille is a municipality in eastern Belgium known for its scenic Ardennes landscapes and outdoor recreation opportunities.
-
B.
Waunarlwydd
Waunarlwydd is a suburban village and community on the western edge of Swansea in South Wales, known for its residential character and local amenities.
-
C.
Aulnat
Aulnat is a commune in central France situated in the Puy-de-Dôme department within the Auvergne region.
-
D.
Arvegil
Arvegil is a fictional Dúnedain king of Arnor in J.R.R. Tolkien’s legendarium, descended from Isildur.
-
E.
Wanlaweyn
Wanlaweyn is a town in southern Somalia that serves as an important local center within the Lower Shabelle 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389598848190ba15e6eea2ba2903 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:49 a.m.