Triple
T31803376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Broadcast |
E811802
|
entity |
| Predicate | hasSpokenWord |
P98558
|
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: [The Broadcast, hasSpokenWord, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenWord Context triple: [The Broadcast, hasSpokenWord, yes]
-
A.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
D.
hasSpokenWordVerses
chosen
Indicates that an entity (such as a work or recording) contains or features verses performed in spoken word form.
-
E.
hasSpokenStandard
Indicates that an entity has spoken using a recognized standard form of a language (e.g., standard dialect or official register).
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 30, 2026, 11:42 p.m.