Triple
T29579761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Howell |
E753543
|
entity |
| Predicate | channelLaunchDate |
P180
|
FINISHED |
| Object | danisnotonfire: 2009-10-16 |
—
|
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: danisnotonfire: 2009-10-16 | Statement: [Dan Howell, channelLaunchDate, danisnotonfire: 2009-10-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelLaunchDate Context triple: [Dan Howell, channelLaunchDate, danisnotonfire: 2009-10-16]
-
A.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
launchEndDate
Indicates the date on which a launch activity or campaign is completed or comes to an end.
-
C.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
D.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
E.
launchDatePrecision
Indicates the level of exactness (such as year, month, or day) with which the launch date of something is specified.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d78f2fc8190bc7def38615f2407 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:05 p.m.