Triple
T11082844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Beatrice |
E262044
|
entity |
| Predicate | roleAfterDeposition |
P97116
|
FINISHED |
| Object | Jacobite queen in exile |
—
|
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: Jacobite queen in exile | Statement: [Maria Beatrice, roleAfterDeposition, Jacobite queen in exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterDeposition Context triple: [Maria Beatrice, roleAfterDeposition, Jacobite queen in exile]
-
A.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
B.
roleAfterManaging
Indicates the role or position an entity assumes after it has finished managing another entity or activity.
-
C.
roleAfterRefounding
Indicates the role or position an entity holds following the refounding or re-establishment of an organization, institution, or similar entity.
-
D.
laterRepresented
Indicates that one entity subsequently served as an official representative or agent for another entity at a later time.
-
E.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799bf89f48190889f08d2f5dd220a |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.