Triple
T2918933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linares y Pombo |
E78672
|
entity |
| Predicate | surnameCategory |
P17126
|
FINISHED |
| Object | Spanish compound surnames |
—
|
LITERAL FINISHED |
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 compound surnames | Statement: [Linares y Pombo, surnameCategory, Spanish compound surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameCategory Context triple: [Linares y Pombo, surnameCategory, Spanish compound surnames]
-
A.
familyNameCategory
chosen
Indicates that an entity is associated with a particular classification or grouping based on its family name.
-
B.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
C.
surnameVariant
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
D.
surnamePortmanteauOf
Indicates that one surname is formed as a portmanteau by blending parts of two or more other surnames.
-
E.
patronymicName
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.