Triple
T12501251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonso XIII |
E298826
|
entity |
| Predicate | wasMonarchAtBirth |
P55301
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alfonso XIII, wasMonarchAtBirth, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMonarchAtBirth Context triple: [Alfonso XIII, wasMonarchAtBirth, true]
-
A.
monarchDuringBirth
chosen
Indicates that one entity was the reigning monarch at the time another entity was born.
-
B.
currentMonarchBirthDate
Indicates the date on which the person who is the current monarch of a specified realm was born.
-
C.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
D.
monarchOnEstablishment
Indicates that a particular monarch holds or held the position of head of state for a given establishment (such as a country, state, or institution).
-
E.
ascendedToThroneAs
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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.