Triple
T3869315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohře |
E91943
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Eger |
E338315
|
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: Eger | Statement: [Ohře, alternativeName, Eger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eger Context triple: [Ohře, alternativeName, Eger]
-
A.
Eger
chosen
Eger is a historic city in northern Hungary known for its baroque architecture, castle, and wine culture.
-
B.
Sátoraljaújhely
Sátoraljaújhely is a historic town in northeastern Hungary near the Slovak border, known for its wine region, cultural heritage, and scenic Zemplén Mountains setting.
-
C.
Tiszaújváros
Tiszaújváros is an industrial town in northeastern Hungary known for its large chemical and energy industries and its location along the Tisza River.
-
D.
Sopron
Sopron is a historic city in western Hungary near the Austrian border, known for its well-preserved medieval old town and wine-making traditions.
-
E.
Kaposvár
Kaposvár is a city in southwestern Hungary that serves as the administrative and cultural center of Somogy County.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec533828819080f52dae15fdbecd |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512440b8c8190ae2048bfcdd565ec |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.