Triple
T30102100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | María Teresa, Grand Duchess of Luxembourg |
E765024
|
entity |
| Predicate | reignAsConsortFrom |
P19180
|
FINISHED |
| Object | 2000-10-07 |
—
|
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: 2000-10-07 | Statement: [María Teresa, Grand Duchess of Luxembourg, reignAsConsortFrom, 2000-10-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsConsortFrom Context triple: [María Teresa, Grand Duchess of Luxembourg, reignAsConsortFrom, 2000-10-07]
-
A.
reignAsConsortStart
chosen
Indicates the date or point in time when an individual began their role or tenure as a consort.
-
B.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
-
C.
reignAsQueenConsort
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
D.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
E.
successorAsConsort
Indicates that one individual became the next consort (spouse or partner in an official capacity) following another in a succession.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 7:08 p.m.