Triple
T16206108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tábor District |
E393331
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Tábor |
E299973
|
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: Tábor | Statement: [Tábor District, capital, Tábor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tábor Context triple: [Tábor District, capital, Tábor]
-
A.
Tábor
chosen
Tábor is a historic Czech town best known as a major stronghold and center of the radical Hussite movement in the early 15th century.
-
B.
Tuřany
Tuřany is a district of the Czech city of Brno, known for hosting the region’s main international airport.
-
C.
Tuchkovo
Tuchkovo is an urban-type settlement in Moscow Oblast, Russia, located west of Moscow and known for its proximity to the Ruza Reservoir and regional transport links.
-
D.
Turośl
Turośl is a village in northern Poland located within the Warmian-Masurian Voivodeship, a region known for its lakes and forests.
-
E.
Chocim
Chocim is a historic town in present-day Ukraine, best known as the site of major 17th-century battles between the Polish-Lithuanian Commonwealth and the Ottoman Empire.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270f047c819084645da27759a3d2 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00078fa2ac8190a0a2cf38bc41498d |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.