Triple
T22536376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My 1st Song |
E557164
|
entity |
| Predicate | containsSpokenIntro |
P9712
|
FINISHED |
| Object | The Notorious B.I.G. interview excerpt |
—
|
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: The Notorious B.I.G. interview excerpt | Statement: [My 1st Song, containsSpokenIntro, The Notorious B.I.G. interview excerpt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpokenIntro Context triple: [My 1st Song, containsSpokenIntro, The Notorious B.I.G. interview excerpt]
-
A.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
B.
includesSpokenPrologue
chosen
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
-
C.
hasLiveSpokenIntroductions
Indicates that one entity provides live, spoken introductory remarks or presentations for another entity or event.
-
D.
hasIntro
Indicates that an entity includes or is associated with an introductory section or opening part.
-
E.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15edbd1ec81908ef26b9e442d1921 |
completed | April 29, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.