Triple
T35336450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hug from Dad |
E1020467
|
entity |
| Predicate | composedToUnderscore |
P109712
|
FINISHED |
| Object | emotional tension |
—
|
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: emotional tension | Statement: [Hug from Dad, composedToUnderscore, emotional tension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedToUnderscore Context triple: [Hug from Dad, composedToUnderscore, emotional tension]
-
A.
designedToUnderscore
chosen
Indicates that something is intentionally created or arranged in order to emphasize, highlight, or draw special attention to another thing.
-
B.
composedTo
Indicates that one entity created or authored another entity, typically a work such as a piece of music, writing, or art.
-
C.
composedFor
Indicates that a creative work (typically a piece of music) was specifically written or created for a particular person, group, event, or purpose.
-
D.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
E.
compositionFrom
Indicates that something is formed or made up from specified constituent parts or materials.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:03 p.m.