Triple
T34657758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benalcázar family |
E890027
|
entity |
| Predicate | familyNameOriginType |
P190703
|
FINISHED |
| Object | toponymic surname |
—
|
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: toponymic surname | Statement: [Benalcázar family, familyNameOriginType, toponymic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameOriginType Context triple: [Benalcázar family, familyNameOriginType, toponymic surname]
-
A.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
-
C.
surnameLikelyOriginRegion
Indicates the geographic region from which a person’s surname is most likely to have originated.
-
D.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
E.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 1, 2026, 2:04 a.m.