Triple
T9174671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Párkány |
E220166
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Štúrovo |
E280505
|
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úrovo | Statement: [Battle of Párkány, location, Štúrovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Štúrovo Context triple: [Battle of Párkány, location, Štúrovo]
-
A.
Štúrovo
chosen
Štúrovo is a Slovak town on the Danube River opposite Esztergom, Hungary, known for its cross-border bridge and thermal spa tourism.
-
B.
Štrkovec
Štrkovec is a residential neighborhood and cadastral area within the Ružinov borough of Bratislava, Slovakia.
-
C.
Staňkov
Staňkov is a small town in the Plzeň Region of the Czech Republic, known for its location on the Radbuza River and its traditional West Bohemian character.
-
D.
Ružomberok
Ružomberok is a town in northern Slovakia known for its location in the Liptov region and its historical and cultural significance.
-
E.
Trebišov
Trebišov is a town in eastern Slovakia known as an administrative and cultural center of the Trebišov District.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa2f9708190a955bf28a4f04004 |
completed | April 1, 2026, 6:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d054a36ef881908079558050c67e7c |
completed | April 4, 2026, midnight |
Created at: March 30, 2026, 7:23 p.m.