Triple
T12569798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domažlice District |
E295570
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Staňkov |
E481676
|
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: Staňkov | Statement: [Domažlice District, hasMunicipality, Staňkov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Staňkov Context triple: [Domažlice District, hasMunicipality, Staňkov]
-
A.
Staňkov
chosen
Staňkov is a small town in the Plzeň Region of the Czech Republic, known for its location on the Radbuza River and its traditional West Bohemian character.
-
B.
Štěnovice
Štěnovice is a municipality and village in the Plzeň Region of the Czech Republic, located just south of the city of Plzeň.
-
C.
Štrkovec
Štrkovec is a residential neighborhood and cadastral area within the Ružinov borough of Bratislava, Slovakia.
-
D.
Štúrovo
Štúrovo is a Slovak town on the Danube River opposite Esztergom, Hungary, known for its cross-border bridge and thermal spa tourism.
-
E.
Studánka
Studánka is a small municipality and village located in the Tachov District of the Plzeň Region in the Czech Republic.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954a422c88190a22cc34d2eac00ce |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6559336088190874123c06c86630e |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 11:50 p.m.