Triple
T21350233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prince of the Hungarians |
E526455
|
entity |
| Predicate | positionHeldBy |
P8
|
FINISHED |
| Object | Fajsz |
—
|
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: Fajsz | Statement: [Grand Prince of the Hungarians, positionHeldBy, Fajsz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fajsz Context triple: [Grand Prince of the Hungarians, positionHeldBy, Fajsz]
-
A.
Fajsz
chosen
Fajsz was a 10th-century Grand Prince of the early Hungarian state, known primarily from medieval chronicles as one of the Árpád dynasty rulers.
-
B.
Feszl
Feszl is a Hungarian surname most notably associated with architect Frigyes Feszl, known for his contributions to 19th-century Hungarian architecture.
-
C.
Friesz
Friesz is a surname most notably associated with the French Fauvist painter Othon Friesz.
-
D.
Szalafő
Szalafő is a traditional rural village in western Hungary known for its preserved folk architecture, scattered farmsteads, and role as a cultural center of the Őrség region.
-
E.
Rábafüzes
Rábafüzes is a small Hungarian village near the Austrian border, known as a key road and rail crossing point between the two countries.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad31087481909d41e9d28286f04d |
completed | April 22, 2026, 11:12 a.m. |
Created at: April 16, 2026, 5:03 p.m.