Triple
T38138944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Save the Life of My Child |
E952425
|
entity |
| Predicate | containsMotifFrom |
P31989
|
FINISHED |
| Object | The Sound of Silence |
E243064
|
NE 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: The Sound of Silence | Statement: [Save the Life of My Child, containsMotifFrom, The Sound of Silence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMotifFrom Context triple: [Save the Life of My Child, containsMotifFrom, The Sound of Silence]
-
A.
usesMotifsFrom
chosen
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
hasTypeOfMotif
Indicates that one entity features or is characterized by a specific kind or category of motif.
-
C.
hasInheritanceMotif
Indicates that one entity incorporates or exhibits a recurring pattern, theme, or feature derived from or passed down by another entity.
-
D.
numberOfMotifs
Indicates the count of distinct motifs associated with or contained within a given entity.
-
E.
bindsSequenceMotif
Indicates that one entity specifically recognizes and attaches to a particular sequence motif of another entity.
- F. None of above.
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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea75108c8190b8db9a40e5138ef2 |
completed | June 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:21 p.m.