Triple
T1930172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Hungary |
E40926
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Esztergom |
E175407
|
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: Esztergom | Statement: [Kingdom of Hungary, capital, Esztergom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esztergom Context triple: [Kingdom of Hungary, capital, Esztergom]
-
A.
Esztergom
chosen
Esztergom is a historic Hungarian city on the Danube River that served as an early royal capital and remains a major religious and cultural center.
-
B.
Gödöllő
Gödöllő is a Hungarian town near Budapest best known for its historic Royal Palace, one of the largest Baroque palaces in Hungary.
-
C.
Székesfehérvár
Székesfehérvár is a historic city in central Hungary that served as a medieval royal seat and coronation site for Hungarian kings.
-
D.
Veszprém
Veszprém is a historic city in western Hungary known for its medieval castle district and role as a regional cultural and administrative center.
-
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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af8342b7688190a626b4f5d3b3807d |
completed | March 10, 2026, 2:34 a.m. |
Created at: March 4, 2026, 7:35 p.m.