Triple
T5750890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napoléon François Charles Joseph Bonaparte |
E126847
|
entity |
| Predicate | recognizedAsEmperorBy |
P16400
|
FINISHED |
| Object | Napoleonic loyalists |
—
|
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: Napoleonic loyalists | Statement: [Napoléon François Charles Joseph Bonaparte, recognizedAsEmperorBy, Napoleonic loyalists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsEmperorBy Context triple: [Napoléon François Charles Joseph Bonaparte, recognizedAsEmperorBy, Napoleonic loyalists]
-
A.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
B.
definedEmperorAs
chosen
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
E.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.