Triple
T29164989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest of Bliss |
E739291
|
entity |
| Predicate | hasNoVoiceoverNarration |
P49712
|
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: [Forest of Bliss, hasNoVoiceoverNarration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoVoiceoverNarration Context triple: [Forest of Bliss, hasNoVoiceoverNarration, true]
-
A.
hasNarration
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
-
B.
hasNoIntertitles
Indicates that the work (typically a film or video) does not contain any intertitles or title cards within its content.
-
C.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
D.
silentWithIntertitles
Indicates that a work is a silent production that conveys dialogue or narrative information through intertitles rather than synchronized spoken sound.
-
E.
hasNoSpokenDialogue
chosen
Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: April 28, 2026, 11:49 a.m.