Triple
T4091314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bács-Bodrog County |
E87708
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Bodrog |
E234401
|
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: Bodrog | Statement: [Bács-Bodrog County, namedAfter, Bodrog]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bodrog Context triple: [Bács-Bodrog County, namedAfter, Bodrog]
-
A.
Bodrog
chosen
Bodrog is a river in Central Europe that flows through Slovakia and Hungary before joining the Tisza River.
-
B.
Ségny
Ségny is a small commune in eastern France’s Ain department, situated near the Swiss border in the Auvergne-Rhône-Alpes region.
-
C.
Sajó River
The Sajó River is a waterway in Central Europe, chiefly in present-day Hungary and Slovakia, historically notable as the site of the Mongol victory over the Kingdom of Hungary at the 1241 Battle of Mohi.
-
D.
Sajó
Sajó is a river in Central Europe that flows through Slovakia and northeastern Hungary before joining the Tisza River.
-
E.
Zala River
The Zala River is a major river in western Hungary that drains a large catchment area before emptying into Lake Balaton.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcac77788190a5e934fe7c46a1fa |
completed | March 9, 2026, 5 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b57f1d1ab081909b7999e8feede458 |
completed | March 14, 2026, 3:30 p.m. |
Created at: March 9, 2026, 3:39 p.m.