Triple
T25158107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There Will Be No Intermission |
E626368
|
entity |
| Predicate | fundingPlatform |
P82609
|
FINISHED |
| Object | Patreon |
—
|
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: Patreon | Statement: [There Will Be No Intermission, fundingPlatform, Patreon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingPlatform Context triple: [There Will Be No Intermission, fundingPlatform, Patreon]
-
A.
donationPlatform
chosen
Indicates a relationship where an entity serves as the platform or service through which a donation is made or processed.
-
B.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
C.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
D.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
-
E.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8a2dcc81908fc6d9f01dbb2c63 |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:30 a.m.