Triple
T28037336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy Millman |
E708444
|
entity |
| Predicate | hasSpinOffWithinShow |
P57669
|
FINISHED |
| Object | When the Whistle Blows |
—
|
NE NERFINISHED |
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: When the Whistle Blows | Statement: [Andy Millman, hasSpinOffWithinShow, When the Whistle Blows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpinOffWithinShow Context triple: [Andy Millman, hasSpinOffWithinShow, When the Whistle Blows]
-
A.
hasSpinOff
Indicates that one entity is a derivative or spin-off product, work, or organization that originated from another entity.
-
B.
hasSpinOffPotential
Indicates that an entity (such as a project, product, or idea) has the capacity to be developed into a separate, independent venture or derivative offering.
-
C.
hasFictionalShowWithinShow
chosen
Indicates that one show contains or features another fictional show within its narrative.
-
D.
hasFranchiseOrSpinOff
Indicates that one work, series, or product is related to another as a franchise entry or a spin-off derived from it.
-
E.
hasSpinOffAttempt
Indicates an attempt has been made to create a spin-off entity, project, or product derived from the original.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 8:22 p.m.