Triple
T4750055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gully |
E105454
|
entity |
| Predicate | videoOnDemandReleaseDate |
P51124
|
FINISHED |
| Object | June 8, 2021 |
—
|
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: June 8, 2021 | Statement: [Gully, videoOnDemandReleaseDate, June 8, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoOnDemandReleaseDate Context triple: [Gully, videoOnDemandReleaseDate, June 8, 2021]
-
A.
streamingReleaseDate
chosen
Indicates the date on which a work (such as a film, show, or album) becomes available to the public via a streaming platform.
-
B.
streamingReleaseYear
Indicates the calendar year in which a work was first made available for streaming on a platform or service.
-
C.
premieredOn
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
-
D.
imageReleaseDate
Indicates the date on which an image was first made publicly available or officially released.
-
E.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c83af48190bd57be79c1505e9d |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.