Triple
T29430448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villalobos Vélez |
E746413
|
entity |
| Predicate | usedAsMaternalSurnameOf |
P189436
|
FINISHED |
| Object | María Guadalupe Villalobos Vélez |
—
|
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: María Guadalupe Villalobos Vélez | Statement: [Villalobos Vélez, usedAsMaternalSurnameOf, María Guadalupe Villalobos Vélez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMaternalSurnameOf Context triple: [Villalobos Vélez, usedAsMaternalSurnameOf, María Guadalupe Villalobos Vélez]
-
A.
usedAsBirthSurnameOf
Indicates that a particular surname served as the family name an individual was born with.
-
B.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
C.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
D.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
-
E.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or group.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 28, 2026, 3:12 p.m.