Triple
T10707557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude of France |
E252445
|
entity |
| Predicate | spouseReignEnd |
P85483
|
FINISHED |
| Object | 1547 |
—
|
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: 1547 | Statement: [Claude of France, spouseReignEnd, 1547]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseReignEnd Context triple: [Claude of France, spouseReignEnd, 1547]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
reignAsKingConsortEnd
chosen
Indicates the point in time or event at which an individual’s tenure as king consort comes to an end.
-
C.
thirdHolderReignEnd
Indicates the date or point in time when the reign or tenure of the third holder of a title, office, or position comes to an end.
-
D.
spouseIsLastIndependentRulerOf
Indicates that the subject’s spouse is recognized as the final ruler of a polity who governed independently, before loss of sovereignty or incorporation into another authority.
-
E.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fde080d48190830eaa863aad61ff |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:12 p.m.