Triple
T18265473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem, Baden-Württemberg |
E437471
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Grasbeuren |
—
|
NE NERFINISHED |
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: Grasbeuren | Statement: [Salem, Baden-Württemberg, hasSubdivision, Grasbeuren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grasbeuren Context triple: [Salem, Baden-Württemberg, hasSubdivision, Grasbeuren]
-
A.
Grasbeuren
chosen
Grasbeuren is a former locality in the German state of Baden-Württemberg that was incorporated into the municipality of Salem.
-
B.
Goeferdinge
Goeferdinge is a village in the Flemish province of East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
-
C.
Zandhoven
Zandhoven is a municipality in the Belgian province of Antwerp, known for its rural character and village communities.
-
D.
Beelen
Beelen is a small municipality in the German state of North Rhine-Westphalia, known for its rural character and location within the Münsterland region.
-
E.
Horebeke
Horebeke is a small rural municipality in the Flemish Ardennes region of East Flanders, Belgium.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff79851481909a4bbeb14fb00647 |
completed | April 19, 2026, 4:14 p.m. |
Created at: April 10, 2026, 10:34 a.m.