Triple
T10793144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonso I of Aragon |
E254632
|
entity |
| Predicate | marriageStartWithUrracaOfLeónAndCastile |
P95516
|
FINISHED |
| Object | 1109 |
—
|
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: 1109 | Statement: [Alfonso I of Aragon, marriageStartWithUrracaOfLeónAndCastile, 1109]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageStartWithUrracaOfLeónAndCastile Context triple: [Alfonso I of Aragon, marriageStartWithUrracaOfLeónAndCastile, 1109]
-
A.
reignAsQueenConsortOfSpainStart
Indicates the time at which a person began their tenure as queen consort of Spain.
-
B.
successorAsQueenOfCastile
Indicates that one entity became the next reigning queen of Castile following another entity.
-
C.
reignAsQueenConsortOfNavarreStart
Indicates the time at which a person begins their tenure as queen consort of Navarre.
-
D.
successorAsQueenOfAragon
Indicates that one person became the next reigning queen of Aragon after another person.
-
E.
reignEndAsKingOfCastile
Indicates the date or event when an individual’s rule as King of Castile comes to an end.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f7ad408190af4727dd9d459498 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.