Triple
T25942941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Henry of Battenberg |
E653755
|
entity |
| Predicate | issueSpouse |
P13
|
FINISHED |
| Object | King Alfonso XIII of Spain |
—
|
NE NERFINISHED |
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: King Alfonso XIII of Spain | Statement: [Princess Henry of Battenberg, issueSpouse, King Alfonso XIII of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueSpouse Context triple: [Princess Henry of Battenberg, issueSpouse, King Alfonso XIII of Spain]
-
A.
spouse
chosen
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
throughSpouse
Indicates a relationship or connection that exists indirectly between two entities by way of one entity’s spouse.
-
C.
spouseAction
Indicates that one person performs an action toward or on their spouse within the context of a marital relationship.
-
D.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
E.
maritalIssue
Indicates a relationship where there is conflict, dissatisfaction, or significant strain within a marital or committed partnership.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 8:41 a.m.