Triple
T33549014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasilyevna |
E859283
|
entity |
| Predicate | fatherNameRequirement |
P143342
|
FINISHED |
| Object | father named Vasily |
—
|
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: father named Vasily | Statement: [Vasilyevna, fatherNameRequirement, father named Vasily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherNameRequirement Context triple: [Vasilyevna, fatherNameRequirement, father named Vasily]
-
A.
nameRequirement
Indicates that there is a specified condition or constraint that a name must satisfy.
-
B.
legitimacyRequirement
Indicates that certain conditions or criteria must be met for an action, status, or authority to be considered valid or legitimate.
-
C.
fatherName
Indicates that one entity is the name of the father of another entity.
-
D.
fatherCondition
chosen
Indicates a condition, state, or requirement specifically associated with the father in a given relationship or context.
-
E.
nameGivenByFather
Indicates that a father is the one who assigned or chose the given name for a particular person.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:39 a.m.