Triple
T28921343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brey |
E733520
|
entity |
| Predicate | positionInSpanishNamingCustom |
P1082
|
FINISHED |
| Object | second 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: second surname | Statement: [Brey, positionInSpanishNamingCustom, second surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSpanishNamingCustom Context triple: [Brey, positionInSpanishNamingCustom, second surname]
-
A.
followsIberianNamingCustom
Indicates that a person’s full name is structured according to Iberian naming customs, typically including given names followed by multiple family surnames in a culturally specific order.
-
B.
fractionalNameInSpanish
Indicates that an entity’s fractional value is expressed or named in the Spanish language.
-
C.
hasNameInSpanish
Indicates that an entity is associated with a specific name expressed in the Spanish language.
-
D.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
E.
rankInSpanishHonoursSystem
Indicates the specific hierarchical position a person holds within the system of Spanish honors and decorations.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 8:19 a.m.