Triple
T35083434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urdangarin family |
E1012513
|
entity |
| Predicate | maritalLink |
P64467
|
FINISHED |
| Object | Spanish royal family |
—
|
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: Spanish royal family | Statement: [Urdangarin family, maritalLink, Spanish royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalLink Context triple: [Urdangarin family, maritalLink, Spanish royal family]
-
A.
maritalRelations
chosen
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
D.
characterRelativeByMarriage
Indicates that one character is related to another through marriage rather than by blood.
-
E.
maritalPeriodWith
Indicates the time span during which two entities were married to each other.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.