Triple
T6036580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napoleon I (as heir) |
E134435
|
entity |
| Predicate | hasSecondReignEndAsEmperor |
P2721
|
FINISHED |
| Object | 22 June 1815 |
—
|
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: 22 June 1815 | Statement: [Napoleon I (as heir), hasSecondReignEndAsEmperor, 22 June 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondReignEndAsEmperor Context triple: [Napoleon I (as heir), hasSecondReignEndAsEmperor, 22 June 1815]
-
A.
endEmperor
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
B.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
previousEmperorReignName
Indicates that the subject emperor’s reign name immediately precedes the object emperor’s reign name in historical succession.
-
D.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
E.
reignAsHolyRomanEmperorEnd
Indicates the time or event at which an entity’s tenure as Holy Roman Emperor comes to an end.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056cb06508190a90beb4d9d083835 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.