Triple
T24430250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eli Sachs |
E615982
|
entity |
| Predicate | hasFamilyDynamic |
P156091
|
FINISHED |
| Object | intrusive family |
—
|
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: intrusive family | Statement: [Eli Sachs, hasFamilyDynamic, intrusive family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyDynamic Context triple: [Eli Sachs, hasFamilyDynamic, intrusive family]
-
A.
belongsToDynamicalFamily
Indicates that one entity is a member of, or classified within, a specific dynamical family defined by shared motion or evolution characteristics.
-
B.
hasParentChildDynamicWith
Indicates a relationship in which one entity assumes a parental role and the other assumes a child role, involving hierarchical care, guidance, or authority dynamics between them.
-
C.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
E.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296aab8948190b9cb869bab71fb4c |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:15 a.m.