Triple
T14756230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trenčín Region |
E346735
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Bojnice |
E1073590
|
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: Bojnice | Statement: [Trenčín Region, containsTown, Bojnice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bojnice Context triple: [Trenčín Region, containsTown, Bojnice]
-
A.
Bojnice
chosen
Bojnice is a historic spa town in central Slovakia best known for its fairy-tale Bojnice Castle and popular zoo.
-
B.
Trebišov
Trebišov is a town in eastern Slovakia known as an administrative and cultural center of the Trebišov District.
-
C.
Banská Belá
Banská Belá is a historic village in central Slovakia known for its long-standing association with the region’s mining industry.
-
D.
Znojmo
Znojmo is a historic town in the South Moravian Region of the Czech Republic, known for its medieval architecture, wine production, and strategic position near the Austrian border.
-
E.
Ružomberok
Ružomberok is a town in northern Slovakia known for its location in the Liptov region and its historical and cultural significance.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa11f77788190866e0820d33af588 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 1:30 a.m.