Triple
T8060746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Adelaide of Savoy |
E188112
|
entity |
| Predicate | spouseOfHeirApparentTo |
P44044
|
FINISHED |
| Object | French throne |
—
|
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: French throne | Statement: [Maria Adelaide of Savoy, spouseOfHeirApparentTo, French throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfHeirApparentTo Context triple: [Maria Adelaide of Savoy, spouseOfHeirApparentTo, French throne]
-
A.
marriedToFutureMonarch
chosen
Indicates that one person is married to another person who will become a monarch in the future.
-
B.
siblingOrConsort
Indicates that two entities are related either as siblings (sharing at least one parent) or as consorts (spouses/partners in a marital or analogous union).
-
C.
heirApparentOf
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
-
D.
successorAsQueenConsort
Indicates that one individual became the next queen consort following another in a royal succession.
-
E.
monarchConsortOf
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcc61c0819085edc26e75c5f6d5 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.