Triple
T35062564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri, Count of Chambord |
E1011632
|
entity |
| Predicate | offeredThroneAfter |
P58020
|
FINISHED |
| Object | fall of Napoleon III |
—
|
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: fall of Napoleon III | Statement: [Henri, Count of Chambord, offeredThroneAfter, fall of Napoleon III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredThroneAfter Context triple: [Henri, Count of Chambord, offeredThroneAfter, fall of Napoleon III]
-
A.
offeredCrownTo
chosen
Indicates that one entity formally presented or proposed a royal crown or rulership to another entity.
-
B.
invitedToThrone
Indicates that one entity has been formally asked or summoned to be present at, or potentially take a role in, a throne or royal seat of power.
-
C.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
D.
offeredCrownOutcome
Indicates the outcome or result that followed from an offer of a crown or rulership being made to someone.
-
E.
soughtThroneOf
Indicates that one entity actively attempted to obtain, claim, or gain control of the throne associated with another entity.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:01 p.m.