Triple

T16066122
Position Surface form Disambiguated ID Type / Status
Subject Károly Király E389735 entity
Predicate givenName P17 FINISHED
Object Károly E79472 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ároly | Statement: [Károly Király, givenName, Károly]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Károly
Context triple: [Károly Király, 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. 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.
  • D. 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.
  • E. Mátyás
    Mátyás is a Hungarian given name most notably borne by Mátyás Rákosi, the communist leader who dominated Hungary’s politics in the early Cold War era.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1837ca628819081dfc439fe322d58 completed April 17, 2026, 12:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff798c2a48190b6eccd476a0a396f completed May 10, 2026, 3:12 a.m.
Created at: April 10, 2026, 4:57 a.m.