Triple
T4685065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelly West |
E103900
|
entity |
| Predicate | hasFamilyRelationship |
P38221
|
FINISHED |
| Object | daughter of Dottie West |
—
|
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 of Dottie West | Statement: [Shelly West, hasFamilyRelationship, daughter of Dottie West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyRelationship Context triple: [Shelly West, hasFamilyRelationship, daughter of Dottie West]
-
A.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
D.
hasFamilyRelationInWork
Indicates that there exists a family relationship between two entities within the context of a specific work (e.g., book, film, or other creative work).
-
E.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.