Triple
T21350245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prince of the Hungarians |
E526455
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Etelköz |
—
|
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: Etelköz | Statement: [Grand Prince of the Hungarians, residence, Etelköz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Etelköz Context triple: [Grand Prince of the Hungarians, residence, Etelköz]
-
A.
Etelköz
chosen
Etelköz was the historical region in Eastern Europe where the migrating Magyars settled before conquering the Carpathian Basin.
-
B.
Ercsi
Ercsi is a small town in central Hungary situated along the Danube River in Fejér County.
-
C.
Zólyom
Zólyom is the historical Hungarian name for the Slovak town of Zvolen, an important medieval center in central Slovakia.
-
D.
Echteld
Echteld is a village and former municipality in the Dutch province of Gelderland, now part of the municipality of Neder-Betuwe.
-
E.
Hollókő
Hollókő is a UNESCO World Heritage-listed Hungarian village renowned for its well-preserved traditional Palóc architecture and living rural culture.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad31087481909d41e9d28286f04d |
completed | April 22, 2026, 11:12 a.m. |
Created at: April 16, 2026, 5:03 p.m.