Triple
T23229552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hechingen |
E581111
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Stetten |
—
|
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: Stetten | Statement: [Hechingen, hasSubdivision, Stetten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stetten Context triple: [Hechingen, hasSubdivision, Stetten]
-
A.
Stetten
Stetten is a small municipality in the Bodenseekreis district of the German state of Baden-Württemberg, near Lake Constance.
-
B.
Stetten
chosen
Stetten is a locality within the town of Lichtenfels in the German state of Bavaria.
-
C.
Feldstetten
Feldstetten is a village in the Swabian Alb region of Baden-Württemberg, Germany, that forms part of the town of Laichingen.
-
D.
Niederstetten
Niederstetten is a small town in the Main-Tauber district of Baden-Württemberg, Germany, known for its rural setting and historic architecture.
-
E.
Altstetten
Altstetten is a district of the city of Zurich in Switzerland, known as a major residential and transport hub in the Limmat Valley region.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1923131c081909c6e84b1a0c32e0d |
completed | April 29, 2026, 5:08 a.m. |
Created at: April 17, 2026, 4:09 p.m.