Triple
T26353422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie-Josèphe de Saxe |
E662964
|
entity |
| Predicate | spouseOfHeirApparent |
P104869
|
FINISHED |
| Object | Louis, Dauphin of France |
—
|
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: Louis, Dauphin of France | Statement: [Marie-Josèphe de Saxe, spouseOfHeirApparent, Louis, Dauphin of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfHeirApparent Context triple: [Marie-Josèphe de Saxe, spouseOfHeirApparent, Louis, Dauphin of France]
-
A.
spouseOfHeirToThrone
chosen
Indicates that one person is the married partner of an individual who is the heir to a throne.
-
B.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
C.
spouseIsMonarchOf
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
-
D.
regentSpouse
Indicates that one person is the spouse of a regent, i.e., married to an individual who rules on behalf of a monarch or in place of the sovereign.
-
E.
spouseServedMonarch
Indicates that the spouse of a person held a position of service or duty to a 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 10:47 p.m.