Triple
T34995485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles VI |
E1009514
|
entity |
| Predicate | successorInHungary |
P65697
|
FINISHED |
| Object | Maria Theresa |
—
|
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: Maria Theresa | Statement: [Charles VI, successorInHungary, Maria Theresa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInHungary Context triple: [Charles VI, successorInHungary, Maria Theresa]
-
A.
successorInAustria
Indicates that one entity directly follows another in a succession or sequence specifically within the context of Austria (e.g., in an office, role, or position).
-
B.
successorAsKingOfHungary
chosen
Indicates that one person became the next king of Hungary following another person in the royal succession.
-
C.
successorAsPresidentOfHungary
Indicates that one person became the next President of Hungary after another person.
-
D.
predecessorAsKingOfHungary
Indicates that one person previously held the position of King of Hungary immediately before another person.
-
E.
successorAsDukeOfAustria
Indicates that one entity became the next holder of the title Duke of Austria after another entity.
- F. None of above.
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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: May 3, 2026, 4:01 p.m.