Triple
T27158727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will You Be There |
E682595
|
entity |
| Predicate | containsSpokenSection |
P108014
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Will You Be There, containsSpokenSection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpokenSection Context triple: [Will You Be There, containsSpokenSection, yes]
-
A.
hasSpokenWordSections
chosen
Indicates that something contains or includes sections where words are spoken rather than sung or played.
-
B.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
C.
includesSpokenPrologue
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
-
D.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
E.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 27, 2026, 9:17 a.m.