Triple
T15396857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalina de Aragón |
E368197
|
entity |
| Predicate | motivoDeAnulación |
P28641
|
FINISHED |
| Object | faltaDeHerederoVarón |
—
|
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: faltaDeHerederoVarón | Statement: [Catalina de Aragón, motivoDeAnulación, faltaDeHerederoVarón]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motivoDeAnulación Context triple: [Catalina de Aragón, motivoDeAnulación, faltaDeHerederoVarón]
-
A.
reasonForAnnulment
chosen
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
B.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
-
C.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
D.
aimOfAnnulment
Indicates that an action or legal measure has the purpose or objective of nullifying, canceling, or invalidating something.
-
E.
reasonForReversal
Indicates the specific cause or justification for undoing, overturning, or reversing a prior decision, action, or outcome.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8c5d40819086622b70edcb6294 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.