Triple
T35712647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonty |
E1031908
|
entity |
| Predicate | hasPatronymicFeminineForm |
P84827
|
FINISHED |
| Object | Leontyevna |
—
|
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: Leontyevna | Statement: [Leonty, hasPatronymicFeminineForm, Leontyevna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronymicFeminineForm Context triple: [Leonty, hasPatronymicFeminineForm, Leontyevna]
-
A.
hasPatronymicDerivative
chosen
Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
-
B.
hasPatronymicUse
Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
-
C.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
D.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
E.
usesPatronymicPrefix
Indicates that one entity forms or refers to a person’s name using a patronymic prefix derived from their father’s (or ancestor’s) 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:05 p.m.