Triple
T25748853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I: Eternal Sunshine (The Pledge) |
E648414
|
entity |
| Predicate | hasNoTraditionalChorus |
P184353
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Act I: Eternal Sunshine (The Pledge), hasNoTraditionalChorus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoTraditionalChorus Context triple: [Act I: Eternal Sunshine (The Pledge), hasNoTraditionalChorus, true]
-
A.
hasChorusOnlyStructure
Indicates that the musical work is structured solely as a chorus section, without distinct verses, bridges, or other formal sections.
-
B.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
C.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
D.
hasVerseChorusStructure
Indicates that something, typically a musical composition, is organized using a recurring pattern of verses and choruses.
-
E.
hasChantLikeChorus
Indicates that one element features or is characterized by a chorus section that is chant-like in style or delivery.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 22, 2026, 4:32 a.m.