Triple
T26876938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christina Alexandra |
E676776
|
entity |
| Predicate | reignStartAsRulingMonarch |
P50036
|
FINISHED |
| Object | 1644 |
—
|
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: 1644 | Statement: [Christina Alexandra, reignStartAsRulingMonarch, 1644]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsRulingMonarch Context triple: [Christina Alexandra, reignStartAsRulingMonarch, 1644]
-
A.
reignStartAsKing
Indicates the time or event at which an individual begins their reign in the role of king.
-
B.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
C.
reignAsCoRulerStart
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
D.
reignAsRegentStart
Indicates the point in time when an individual begins exercising ruling authority as a regent on behalf of another.
-
E.
ascendedToThroneAs
chosen
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 5:36 a.m.