Triple
T29148606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bent (TV series) |
E738839
|
entity |
| Predicate | originalRunChannelType |
P125731
|
FINISHED |
| Object | broadcast television |
—
|
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: broadcast television | Statement: [Bent (TV series), originalRunChannelType, broadcast television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRunChannelType Context triple: [Bent (TV series), originalRunChannelType, broadcast television]
-
A.
originalRunType
Indicates the initial or primary category or mode under which a particular run, execution, or process was originally conducted.
-
B.
originalChannel
Indicates the communication channel or medium through which something was first created, sent, or published.
-
C.
originalChannelCategory
chosen
Indicates the category or type of channel an item or communication originally belonged to before any changes or reclassification.
-
D.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
E.
originalChannelOnFirstRun
Indicates that the specified channel is the one initially used or active when the system or application is run for the first time.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: April 28, 2026, 11:41 a.m.