Triple
T29578913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French legitimism |
E753519
|
entity |
| Predicate | consideredUsurper |
P168663
|
FINISHED |
| Object | Louis-Philippe I |
—
|
NE NERFINISHED |
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: Louis-Philippe I | Statement: [French legitimism, consideredUsurper, Louis-Philippe I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredUsurper Context triple: [French legitimism, consideredUsurper, Louis-Philippe I]
-
A.
usurpsThroneFrom
Indicates that one entity seizes control of a throne or rulership position that previously belonged to another entity, typically by force or illegitimate means.
-
B.
notableUsurperDuringReign
Indicates that a specified person is a notable usurper who attempted to seize or seized power during the reign of a particular ruler.
-
C.
usurperOnLosingSide
Indicates that the usurper was aligned with the faction or side that ultimately lost in a conflict or power struggle.
-
D.
usurpedFrom
Indicates that one entity has taken power, position, or property from another entity illegitimately or by force.
-
E.
usurperInRegion
Indicates that an entity has unlawfully taken or holds power or authority within a specified region.
- F. None of above. chosen
Provenance (4 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 6:05 p.m.