Triple
T14210323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | István Széchenyi |
E352210
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | István |
E128847
|
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: István | Statement: [István Széchenyi, givenName, István]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: István Context triple: [István Széchenyi, givenName, István]
-
A.
István
chosen
István is the Hungarian given name of Stephen I of Hungary, the first Christian king and founder of the medieval Hungarian state.
-
B.
Gyula
Gyula is a Hungarian masculine given name historically borne by several notable political and cultural figures.
-
C.
Lajos
Lajos is a Hungarian masculine given name commonly used in Central and Eastern Europe.
-
D.
László
László is a Hungarian given name most famously borne by the avant-garde artist and Bauhaus teacher László Moholy-Nagy.
-
E.
Imre
Imre is a Hungarian given name most famously borne by Imre Nagy, the reformist prime minister associated with the 1956 Hungarian Revolution.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61fa8d24819092a8ec5d34c1c799 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c29b4e08190896ddde5096628d3 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:05 a.m.