Triple
T16089261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikuláš of Kadaň |
E390316
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Kadaň |
E752886
|
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: Kadaň | Statement: [Mikuláš of Kadaň, residence, Kadaň]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kadaň Context triple: [Mikuláš of Kadaň, residence, Kadaň]
-
A.
Kadaň
chosen
Kadaň is a historic town in the northwestern Czech Republic, known for its well-preserved medieval center and location on the Ohře River.
-
B.
Orekhovets
Orekhovets is an alternative name for Oreshek, a historic Russian fortress located at the source of the Neva River near Lake Ladoga.
-
C.
Terekhovo
Terekhovo is a metro station on Moscow’s Big Circle Line, serving the Terekhovo area in the western part of the city.
-
D.
Kirovakan
Kirovakan is the former name of Vanadzor, a major industrial city in northern Armenia.
-
E.
Dyatkovo
Dyatkovo is a town in western Russia known historically for its glassmaking industry and as an administrative center within Bryansk Oblast.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1845161908190adca2af94710b2cc |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb934b448190a486401ac6c01065 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:59 a.m.