Triple
T14957826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happily Ever After (song) |
E372977
|
entity |
| Predicate | basedOnMotif |
P31989
|
FINISHED |
| Object | fairy-tale happy ending |
—
|
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: fairy-tale happy ending | Statement: [Happily Ever After (song), basedOnMotif, fairy-tale happy ending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnMotif Context triple: [Happily Ever After (song), basedOnMotif, fairy-tale happy ending]
-
A.
usesMotifsFrom
chosen
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
featuresMotif
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
D.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
E.
basedOnComposition
Indicates that one entity is determined, derived, or defined according to the constituent parts or composition of another entity.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cd85bc81909040b7ff78f62554 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.