Triple
T9196896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostallgäu |
E220737
|
entity |
| Predicate | administrativeSeat |
P21613
|
FINISHED |
| Object | Marktoberdorf |
E773414
|
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: Marktoberdorf | Statement: [Ostallgäu, administrativeSeat, Marktoberdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marktoberdorf Context triple: [Ostallgäu, administrativeSeat, Marktoberdorf]
-
A.
Marktoberdorf
chosen
Marktoberdorf is a small Bavarian town in southern Germany known as an administrative and cultural center in the Allgäu region.
-
B.
Altoberndorf
Altoberndorf is a district or locality within the town of Oberndorf am Neckar in the German state of Baden-Württemberg.
-
C.
Betzdorf
Betzdorf is a commune in eastern Luxembourg known for its residential areas, railway facilities, and the presence of Betzdorf Castle.
-
D.
Burgstädt
Burgstädt is a small town in the German state of Saxony, known for its traditional architecture and location near the city of Chemnitz.
-
E.
Hubersdorf
Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87d6460819097234b5dd3f749b4 |
completed | April 1, 2026, 8:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d077797be081908300a5baa0041ce5 |
completed | April 4, 2026, 2:29 a.m. |
Created at: March 30, 2026, 7:25 p.m.