Triple
T29579762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Howell |
E753543
|
entity |
| Predicate | subscriberMilestone |
P52327
|
FINISHED |
| Object | danisnotonfire: 1 million subscribers by 2012 |
—
|
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: 1 million subscribers by 2012 | Statement: [Dan Howell, subscriberMilestone, danisnotonfire: 1 million subscribers by 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subscriberMilestone Context triple: [Dan Howell, subscriberMilestone, danisnotonfire: 1 million subscribers by 2012]
-
A.
hitsMilestone
chosen
Indicates that an entity reaches or achieves a predefined milestone or target in a process, project, or progression.
-
B.
marketingMilestone
Indicates a significant event or achievement within a marketing effort that marks progress toward marketing goals or phases.
-
C.
coachMilestone
Indicates that a coach has reached or achieved a specific milestone or notable point in their coaching career or tenure.
-
D.
typeOfMilestone
Indicates that one entity is a specific kind or category of milestone in relation to another entity.
-
E.
salesMilestone
Indicates that a specific sales target or threshold has been reached or surpassed.
- 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.