Triple
T11110261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepinster |
E262735
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Verviers |
E176726
|
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: Verviers | Statement: [Pepinster, locatedNear, Verviers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Verviers Context triple: [Pepinster, locatedNear, Verviers]
-
A.
Verviers
chosen
Verviers is a city in eastern Belgium known historically for its textile industry and as a regional center in the province of Liège.
-
B.
Durbuy
Durbuy is a small, picturesque town in the Belgian Ardennes often promoted as one of the “smallest cities in the world,” known for its medieval architecture and tourism.
-
C.
Buizingen
Buizingen is a village and suburb of Halle in Flemish Brabant, Belgium, known in part for the 2010 train collision that occurred near its railway station.
-
D.
Binche
Binche is a historic town in the Walloon region of Belgium, renowned for its well-preserved medieval architecture and its UNESCO-recognized Carnival of Binche.
-
E.
Porrentruy
Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a6964508190b679303d3b3a4fd6 |
completed | April 9, 2026, 12:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d759bc88190b670c373f3647a41 |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.