Triple
T28032549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalili |
E708310
|
entity |
| Predicate | isPatronymicOrFamilyBased |
P163646
|
FINISHED |
| Object | family-based 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: family-based surname | Statement: [Khalili, isPatronymicOrFamilyBased, family-based surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatronymicOrFamilyBased Context triple: [Khalili, isPatronymicOrFamilyBased, family-based surname]
-
A.
isPatronymicIn
Indicates that a name or term is used as a patronymic within a specified language, culture, or naming system.
-
B.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
C.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
D.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
E.
hasPatronymicUse
Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63c733844819085a729181009c2b6 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:17 p.m.