Triple
T36079378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankl Tshaptshovitsh |
E1043595
|
entity |
| Predicate | familyConcern |
P63314
|
FINISHED |
| Object | daughter’s purity |
—
|
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: daughter’s purity | Statement: [Yankl Tshaptshovitsh, familyConcern, daughter’s purity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyConcern Context triple: [Yankl Tshaptshovitsh, familyConcern, daughter’s purity]
-
A.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
B.
familyInvolvement
chosen
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
C.
familyContext
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
-
D.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
E.
familyBonds
Indicates the existence and nature of familial relationships or kinship ties between entities.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:08 p.m.