Triple
T14957426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drunk History |
E372966
|
entity |
| Predicate | hasSpinOffForm |
P110810
|
FINISHED |
| Object | digital shorts |
—
|
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: digital shorts | Statement: [Drunk History, hasSpinOffForm, digital shorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpinOffForm Context triple: [Drunk History, hasSpinOffForm, digital shorts]
-
A.
hasSpinOff
Indicates that one entity is a derivative or spin-off product, work, or organization that originated from another entity.
-
B.
hasSpinOffFormatElement
chosen
Indicates that one format element is derived as a spin-off or offshoot from another format element.
-
C.
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.
-
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.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cc73848190ac181782b20dc838 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.