Triple
T904483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis XVIII of France |
E19515
|
entity |
| Predicate | secondReignStart |
P1506
|
FINISHED |
| Object | 1815-07-08 |
—
|
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: 1815-07-08 | Statement: [Louis XVIII of France, secondReignStart, 1815-07-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondReignStart Context triple: [Louis XVIII of France, secondReignStart, 1815-07-08]
-
A.
secondMonarchStart
Indicates the point in time when the reign of a second monarch in a sequence begins.
-
B.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
secondMonarch
Indicates that one entity is the second monarch (in chronological order of reign) in relation to another specified realm, dynasty, or succession context.
-
D.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
previousEmperorReignName
Indicates that the subject emperor’s reign name immediately precedes the object emperor’s reign name in historical 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad590d108190b50627e3bba24017 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.