Triple
T17940900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle of Eger |
E448583
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Eger |
—
|
NE NERFINISHED |
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: [Castle of Eger, locatedIn, Eger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eger Context triple: [Castle of Eger, locatedIn, Eger]
-
A.
Eger
chosen
Eger is a historic city in northern Hungary known for its baroque architecture, castle, and wine culture.
-
B.
Eger
Eger is the former German name for the Czech town of Cheb, a historic settlement near the German border in western Bohemia.
-
C.
Egerszalók
Egerszalók is a Hungarian village famous for its thermal springs and striking terraced salt hill spa complex.
-
D.
Gyor
Győr is a historic city in northwestern Hungary, strategically located at the confluence of the Danube, Rába, and Rábca rivers and known as an important regional industrial and cultural center.
-
E.
Eger District
Eger District is an administrative district in northern Hungary centered around the historic city of Eger, known for its wine region and cultural heritage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad95f4608190b1ebb45944218f07 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.