Triple
T25748846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I: Eternal Sunshine (The Pledge) |
E648414
|
entity |
| Predicate | hasDenseLyricism |
P9652
|
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), hasDenseLyricism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDenseLyricism Context triple: [Act I: Eternal Sunshine (The Pledge), hasDenseLyricism, true]
-
A.
hasLyricalStyle
chosen
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
B.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
C.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
D.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
E.
hasExplicitLyrics
Indicates that the referenced content contains explicit language or themes, such as profanity, sexual content, or strong violence.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 4:32 a.m.