Triple
T22145462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Robert of Hungary |
E547275
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Károly |
—
|
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: Károly | Statement: [Charles Robert of Hungary, givenName, Károly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Károly Context triple: [Charles Robert of Hungary, givenName, Károly]
-
A.
Károly
chosen
Károly is the Hungarian form of the given name Charles, commonly used as a male first name in Hungary.
-
B.
Kálmán
Kálmán is a Hungarian surname most notably associated with Rudolf E. Kálmán, the pioneering engineer and mathematician behind the Kalman filter.
-
C.
Lipót
Lipót is a Hungarian masculine given name, historically borne by notable figures such as mathematician Lipót Fejér.
-
D.
Zoltán of Hungary
Zoltán of Hungary was an early 10th-century Grand Prince of the Hungarians from the Árpád dynasty, traditionally regarded as one of the first rulers to consolidate Magyar power in the Carpathian Basin.
-
E.
Károlyi
Károlyi is a Hungarian noble family name most prominently associated with Mihály Károlyi, a key political figure and leader during Hungary’s transition after World War I.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129efd52c8190ab0acff5bbfc0d77 |
completed | April 28, 2026, 9:43 p.m. |
Created at: April 16, 2026, 8:33 p.m.