Triple
T26532841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscar de la Renta |
E670864
|
entity |
| Predicate | hasMaternalFamilyName |
P189436
|
FINISHED |
| Object | Renta Fiallo |
—
|
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: Renta Fiallo | Statement: [Oscar de la Renta, hasMaternalFamilyName, Renta Fiallo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternalFamilyName Context triple: [Oscar de la Renta, hasMaternalFamilyName, Renta Fiallo]
-
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.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
C.
hasAncestralFamilyName
Indicates that an entity bears or is associated with a family name inherited from its ancestors.
-
D.
usedAsMaternalSurnameOf
chosen
Indicates that a surname is used as the maternal (mother’s) family name of a person.
-
E.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 27, 2026, 1:36 a.m.