Triple
T22511674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bourbon |
E556532
|
entity |
| Predicate | lostThroneAgainIn |
P148662
|
FINISHED |
| Object | France in 1830 |
—
|
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: France in 1830 | Statement: [House of Bourbon, lostThroneAgainIn, France in 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostThroneAgainIn Context triple: [House of Bourbon, lostThroneAgainIn, France in 1830]
-
A.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
B.
lostThronesAfter
Indicates that one or more entities ceased to hold their thrones or ruling positions after a specified event, time, or condition.
-
C.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
D.
regainsThroneFrom
Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
-
E.
restoredToThrone
Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d6082e48190a2726907333b6cf1 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:50 p.m.