Triple
T12779238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardennes (Belgium) |
E305458
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Eupen |
E300219
|
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: Eupen | Statement: [Ardennes (Belgium), contains, Eupen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eupen Context triple: [Ardennes (Belgium), contains, Eupen]
-
A.
Eupen
chosen
Eupen is a town in eastern Belgium that serves as the administrative center of the country’s German-speaking Community.
-
B.
Eupen-Malmedy
Eupen-Malmedy is a historically contested, predominantly German-speaking border region that was transferred from Germany to Belgium after World War I and remains part of eastern Belgium today.
-
C.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
-
D.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
E.
Vilvoorde
Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5a5680819095dcd491486d23e7 |
completed | April 10, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7304f62288190aa7788fc6fb04254 |
completed | May 3, 2026, 11:23 a.m. |
Created at: April 9, 2026, 5:29 p.m.