Triple
T12055654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gams |
E287034
|
entity |
| Predicate | hasNeighboringMunicipality |
P224
|
FINISHED |
| Object | Eschen |
E489567
|
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: Eschen | Statement: [Gams, hasNeighboringMunicipality, Eschen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eschen Context triple: [Gams, hasNeighboringMunicipality, Eschen]
-
A.
Eschen
chosen
Eschen is a municipality in northern Liechtenstein known for its residential character and role as one of the country’s larger population centers.
-
B.
Wustermark
Wustermark is a municipality in the Havelland district of Brandenburg, Germany, located west of Berlin and known for its mix of rural character and growing residential and commercial areas.
-
C.
Planegg
Planegg is a municipality in the district of Munich in Bavaria, Germany, known for its scenic location along the Würm River and its proximity to the city of Munich.
-
D.
Erkelenz
Erkelenz is a historic town in western Germany, known for its medieval origins and role as a regional administrative and cultural center.
-
E.
Schorisse
Schorisse is a village in East Flanders, Belgium, that now forms part of the municipality of Maarkedal.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90425258c8190ba7b3b837c439253 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e3ee53c81909c2e4620a12a46da |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:47 p.m.