Triple
T23939638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ortiz |
E602744
|
entity |
| Predicate | isPaternalFamilyNameOf |
P154434
|
FINISHED |
| Object | Leonor, Princess of Asturias |
—
|
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: Leonor, Princess of Asturias | Statement: [Ortiz, isPaternalFamilyNameOf, Leonor, Princess of Asturias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPaternalFamilyNameOf Context triple: [Ortiz, isPaternalFamilyNameOf, Leonor, Princess of Asturias]
-
A.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
B.
isPatronymicIn
Indicates that a name or term is used as a patronymic within a specified language, culture, or naming system.
-
C.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa40398819095e24521f3bf8622 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:08 p.m.