Triple
T14059901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eger |
E338315
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Eger-patak |
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-patak | Statement: [Eger, river, Eger-patak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eger-patak Context triple: [Eger, river, Eger-patak]
-
A.
Eperjes
Eperjes is a historic town in present-day Slovakia, known today as Prešov, which was one of the major urban centers of the former Upper Hungary region.
-
B.
Eger
chosen
Eger is a historic city in northern Hungary known for its baroque architecture, castle, and wine culture.
-
C.
Eger
Eger is the former German name for the Czech town of Cheb, a historic settlement near the German border in western Bohemia.
-
D.
Egling
Egling is a rural Bavarian municipality located in southern Germany, known for its scenic landscapes and proximity to the Alps.
-
E.
Ercsi
Ercsi is a small town in central Hungary situated along the Danube River in Fejér 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb6654850819083262f3fb981eb1a |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:21 p.m.