Triple
T10143073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olive Ostrovsky |
E231633
|
entity |
| Predicate | hasFamilySituation |
P92492
|
FINISHED |
| Object | emotionally distant parents |
—
|
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: emotionally distant parents | Statement: [Olive Ostrovsky, hasFamilySituation, emotionally distant parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilySituation Context triple: [Olive Ostrovsky, hasFamilySituation, emotionally distant parents]
-
A.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
B.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
-
C.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
D.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
E.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
- F. None of above. chosen
Provenance (4 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb273fec8190818707167e031d58 |
completed | April 2, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.