Triple
T11112818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pérez |
E262802
|
entity |
| Predicate | usedAsFamilyName |
P23349
|
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: [Pérez, usedAsFamilyName, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFamilyName Context triple: [Pérez, usedAsFamilyName, yes]
-
A.
usedAsSurname
chosen
Indicates that something functions as a family name borne by a person or group of people.
-
B.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
C.
usedAsBirthSurnameOf
Indicates that a particular surname served as the family name an individual was born with.
-
D.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
E.
adoptedFamilyName
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa523588190a25d241ccc6a9679 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.