Triple
T11353083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelšava |
E268882
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Gemer |
E278192
|
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: Gemer | Statement: [Jelšava, historicalRegion, Gemer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gemer Context triple: [Jelšava, historicalRegion, Gemer]
-
A.
Gemer
chosen
Gemer is a historical and geographical region in southern Slovakia known for its mining heritage, medieval castles, and karst landscapes.
-
B.
Gemerek
Gemerek is a town and district in central Turkey known for its location within Sivas Province on the Anatolian plateau.
-
C.
Geremek
Geremek is a Polish surname most notably associated with Bronisław Geremek, a prominent historian, Solidarity activist, and post-communist foreign minister of Poland.
-
D.
Gery
Gery is a spelling variant of the given name Gerry, typically used as a personal name.
-
E.
Germoe
Germoe is a small rural village and civil parish in west Cornwall, England, known for its historic church and scenic countryside near the coast.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea24489081908fbf47fd2e6d709c |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e543a6e97481909dc77a553b217b4d |
completed | April 19, 2026, 9:05 p.m. |
Created at: April 8, 2026, 9:33 p.m.