Triple
T18891700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unzaga |
E462104
|
entity |
| Predicate | onNameType |
P30898
|
FINISHED |
| Object | patronymic or 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: patronymic or toponymic surname | Statement: [Unzaga, onNameType, patronymic or toponymic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onNameType Context triple: [Unzaga, onNameType, patronymic or toponymic surname]
-
A.
onNameTypeLists
chosen
Indicates that something appears on one or more lists that are categorized or organized by name type.
-
B.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
C.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
D.
supportsNameType
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
E.
nameOf
Indicates that one entity is the name or designation of 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47bbf908190b141e98e3468e908 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.