Triple
T7614113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kulm |
E172317
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Bohemia |
E30190
|
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: Bohemia | Statement: [Battle of Kulm, location, Bohemia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bohemia Context triple: [Battle of Kulm, location, Bohemia]
-
A.
Bohemia
chosen
Bohemia is a historical region in the western part of the modern Czech Republic, long a cultural and political center of Central Europe.
-
B.
Moravia
Moravia is a historical region in the eastern part of the Czech Republic, known for its distinct cultural heritage, wine production, and major cities such as Brno and Olomouc.
-
C.
Moravia
Moravia is a canton in Costa Rica known for its suburban character and proximity to the capital city of San José.
-
D.
Czech lands
The Czech lands are the historical regions of Bohemia, Moravia, and Czech Silesia that form the core territory of today’s Czech Republic.
-
E.
Bohemia region
Bohemia region is a historical region in the western part of the modern Czech Republic, known for its central role in Czech history and culture.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa418ef081908fd17ff367520995 |
completed | March 27, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c87097d3a48190b337ff6906847d4e |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:55 p.m.