Triple
T9480300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kagan |
E228617
|
entity |
| Predicate | isPatronymicOrOccupational |
P28498
|
FINISHED |
| Object | occupational 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: occupational surname | Statement: [Kagan, isPatronymicOrOccupational, occupational surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatronymicOrOccupational Context triple: [Kagan, isPatronymicOrOccupational, occupational surname]
-
A.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
B.
isPatronymicOrToponymic
Indicates that a name or term is derived either from a person's name (patronymic) or from a place name (toponymic).
-
C.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
D.
isOccupationalSurname
chosen
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
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.
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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8016813881908dafc026779c89c4 |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:54 p.m.