Triple
T23919381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "(Si Si) Je Suis un Rock Star" |
E602173
|
entity |
| Predicate | containsSpokenSections |
P108014
|
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: ["(Si Si) Je Suis un Rock Star", containsSpokenSections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpokenSections Context triple: ["(Si Si) Je Suis un Rock Star", containsSpokenSections, true]
-
A.
hasSpokenWordSections
chosen
Indicates that something contains or includes sections where words are spoken rather than sung or played.
-
B.
includesSpokenPrologue
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
-
C.
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.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
hasNarration
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1600248190b38cfc93afb22a73 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:41 p.m.