Triple
T13181862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorski Kotar |
E313748
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Delnice |
E313749
|
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: Delnice | Statement: [Gorski Kotar, hasTown, Delnice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Delnice Context triple: [Gorski Kotar, hasTown, Delnice]
-
A.
Delnice
chosen
Delnice is a small town in western Croatia known as a mountain and winter sports center in the Gorski Kotar region.
-
B.
Kavečany
Kavečany is a borough of Košice in eastern Slovakia, known for its hilly landscape, recreational areas, and proximity to major attractions like the Košice Zoo and ski facilities.
-
C.
Krhanice
Krhanice is a small municipality and village in the Central Bohemian Region of the Czech Republic.
-
D.
Pohořelice
Pohořelice is a small town in the South Moravian Region of the Czech Republic, known for its agricultural surroundings and proximity to the city of Brno.
-
E.
Moravice
Moravice is a river in the northern part of the historical Moravia region of 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c490ed081908ea54edb25c3de90 |
completed | April 10, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a2e415481908ad1036376f702dc |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:15 p.m.