Triple
T9561750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montigny-le-Bretonneux |
E230689
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Wittlich |
E808636
|
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: Wittlich | Statement: [Montigny-le-Bretonneux, hasTwinTown, Wittlich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wittlich Context triple: [Montigny-le-Bretonneux, hasTwinTown, Wittlich]
-
A.
Wittlich
chosen
Wittlich is a small town in the Rhineland-Palatinate region of western Germany, known for its wine production and historic old town.
-
B.
Röthlein
Röthlein is a small municipality in the Schweinfurt district of Bavaria, Germany.
-
C.
Waldeck-Frankenberg
Waldeck-Frankenberg is a rural district in northern Hesse, Germany, known for its scenic landscapes, forests, and small historic towns.
-
D.
Haslach
Haslach is a district or locality that forms part of the town of Oberkirch in the German state of Baden-Württemberg.
-
E.
Haslach
Haslach is a town in southern Germany historically noted as the site of the Battle of Haslach-Jungingen during the Napoleonic Wars.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994d31e08190b139f5ad10d8ea31 |
completed | April 1, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f60aa508190b3966f4b917c41b5 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 30, 2026, 8:03 p.m.