Triple
T21289548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernández Pacheco |
E524748
|
entity |
| Predicate | hasDoubleSurnameForm |
P69803
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fernández Pacheco, hasDoubleSurnameForm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoubleSurnameForm Context triple: [Fernández Pacheco, hasDoubleSurnameForm, yes]
-
A.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
B.
isCompoundSurname
chosen
Indicates that a surname consists of two or more distinct name elements combined into a single family name.
-
C.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
E.
hasMiddleSurnameFrom
Indicates that an entity’s middle surname is derived from, or originates with, another specified 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d882408190a2300327cb73b7f6 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.