Triple
T31351679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast |
E799608
|
entity |
| Predicate | hasReleasePlatform |
P33475
|
FINISHED |
| Object | YouTube |
—
|
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: YouTube | Statement: [Feast, hasReleasePlatform, YouTube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleasePlatform Context triple: [Feast, hasReleasePlatform, YouTube]
-
A.
hasOnlinePlatformRelease
chosen
Indicates that an entity has been released or made available through an online platform or digital service.
-
B.
consoleReleasePlatform
Indicates the specific gaming console or platform on which a particular release of a game or software is made available.
-
C.
teaserReleasePlatform
Indicates the platform or service on which a teaser is released or made available.
-
D.
usReleasePlatform
Indicates the platform on which something is released specifically in the United States.
-
E.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.