Triple
T12710873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zita of Bourbon-Parma |
E303712
|
entity |
| Predicate | startTimeOfReignAsQueenConsortOfHungary |
P73694
|
FINISHED |
| Object | 1916-12-30 |
—
|
LITERAL 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: 1916-12-30 | Statement: [Zita of Bourbon-Parma, startTimeOfReignAsQueenConsortOfHungary, 1916-12-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfReignAsQueenConsortOfHungary Context triple: [Zita of Bourbon-Parma, startTimeOfReignAsQueenConsortOfHungary, 1916-12-30]
-
A.
reignAsQueenConsortOfHungaryStart
chosen
Indicates the time at which an individual began serving as queen consort of Hungary.
-
B.
reignAsQueenConsortOfHungaryEnd
Indicates the time or event at which an individual’s tenure as queen consort of Hungary comes to an end.
-
C.
reignAsQueenConsortOfPolandStart
Indicates the time point or event when an individual began serving as queen consort of Poland.
-
D.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
E.
reignAsCountessConsortStart
Indicates the date or time when an individual began serving as a countess consort.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96207b2d881908314efc3e350aa78 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.