Triple
T28768901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarasova |
E726354
|
entity |
| Predicate | derivedFromPatronymicOrFamilyName |
P163646
|
FINISHED |
| Object | Tarasov |
—
|
NE NERFINISHED |
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: Tarasov | Statement: [Tarasova, derivedFromPatronymicOrFamilyName, Tarasov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromPatronymicOrFamilyName Context triple: [Tarasova, derivedFromPatronymicOrFamilyName, Tarasov]
-
A.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
isPatronymicOrFamilyBased
chosen
Indicates that one entity’s name is derived from or based on the personal or family name of another entity.
-
C.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
D.
hasPatronymicDerivative
Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
-
E.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:14 a.m.