Triple
T32562627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatishchev |
E832267
|
entity |
| Predicate | isFamilyNameOfPerson |
P165168
|
FINISHED |
| Object | Vasily Tatishchev |
—
|
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: Vasily Tatishchev | Statement: [Tatishchev, isFamilyNameOfPerson, Vasily Tatishchev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilyNameOfPerson Context triple: [Tatishchev, isFamilyNameOfPerson, Vasily Tatishchev]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
D.
nameFamily
chosen
Indicates that one entity is the family name (surname) of another entity.
-
E.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c609f1c08190830b42dc4df5ab8d |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.