Triple
T5453034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Grave |
E122412
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Escharen |
E22927
|
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: Escharen | Statement: [municipality of Grave, contains, Escharen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Escharen Context triple: [municipality of Grave, contains, Escharen]
-
A.
Escharen
chosen
Escharen is a village in the Dutch province of North Brabant that was formerly an independent municipality before being incorporated into a larger administrative unit.
-
B.
Eschen
Eschen is a municipality in northern Liechtenstein known for its residential character and role as one of the country’s larger population centers.
-
C.
Schöngarth
Schöngarth is a German surname most notably associated with Eberhard Schöngarth, a high-ranking Nazi SS officer and war criminal during World War II.
-
D.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
E.
Radaur
Radaur is a town in the Yamunanagar district of Haryana, India, known primarily as a local commercial and educational center for surrounding rural areas.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91e170f48190b47419b5e2ff71a4 |
completed | March 20, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf4140248081908c7f42b91579a837 |
completed | March 22, 2026, 1:09 a.m. |
Created at: March 20, 2026, 2:08 p.m.