Triple
T23560912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jim Henson Hour |
E579232
|
entity |
| Predicate | shortRunStatus |
P39416
|
FINISHED |
| Object | cancelled after low ratings |
—
|
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: cancelled after low ratings | Statement: [The Jim Henson Hour, shortRunStatus, cancelled after low ratings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortRunStatus Context triple: [The Jim Henson Hour, shortRunStatus, cancelled after low ratings]
-
A.
hasShortRun
Indicates that an entity has a brief or limited-duration run or operational period.
-
B.
originalRunStatus
chosen
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
C.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
-
D.
shortFormat
Indicates that something is presented in a condensed or abbreviated form compared to its full or standard representation.
-
E.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af680ee88190a23a6f9fed7ae757 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:16 p.m.