Triple
T10442668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Márta Károlyi |
E246206
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Károlyi |
E643813
|
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: Károlyi | Statement: [Márta Károlyi, familyName, Károlyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Károlyi Context triple: [Márta Károlyi, familyName, Károlyi]
-
A.
Károlyi
chosen
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.
-
B.
Miklós
Miklós is a Hungarian masculine given name, equivalent to Nicholas in English.
-
C.
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.
-
D.
Frigyes
Frigyes is a Hungarian masculine given name, notably borne by the influential mathematician Frigyes Riesz.
-
E.
Károly
Károly is the Hungarian form of the given name Charles, commonly used as a male first name in Hungary.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdbd731c819084dfff83b4481ae8 |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d933a2daf481908300a12d0f794e4c |
completed | April 10, 2026, 5:30 p.m. |
Created at: April 6, 2026, 12:15 p.m.