Triple
T19620514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scharnitz |
E470992
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Oberdorf |
—
|
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: Oberdorf | Statement: [Scharnitz, hasSubdivision, Oberdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberdorf Context triple: [Scharnitz, hasSubdivision, Oberdorf]
-
A.
Oberdorf
Oberdorf is a historic quarter within Zurich’s Old Town known for its narrow streets, traditional buildings, and lively mix of shops, restaurants, and cultural venues.
-
B.
Oberdorf
Oberdorf is a Swiss municipality situated in the central alpine canton of Nidwalden.
-
C.
Oberdorf
chosen
Oberdorf is a locality within the Austrian municipality of Wolfurt in the state of Vorarlberg.
-
D.
Oberaudorf
Oberaudorf is a small Bavarian town in southern Germany near the Austrian border, known for its alpine scenery and ski tourism.
-
E.
Oberndorf
Oberndorf is a district or locality within the town of Kuppenheim in the German state of Baden-Württemberg.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e512d08190a76bf81b3282e0e5 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:43 p.m.