Triple
T34867565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What the Bleep Do We Know!? |
E1005054
|
entity |
| Predicate | extendedVersionReleaseYear |
P100051
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [What the Bleep Do We Know!?, extendedVersionReleaseYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedVersionReleaseYear Context triple: [What the Bleep Do We Know!?, extendedVersionReleaseYear, 2006]
-
A.
latestVersionYear
Indicates the calendar year in which the most recent version of an entity (such as a product, document, or software) was released or became available.
-
B.
bestKnownVersionReleaseYear
Indicates the calendar year in which the most widely recognized or prominent version of something was released.
-
C.
ARVersionAnnouncementYear
Indicates the year in which a specific version of an augmented reality (AR) product or system was officially announced.
-
D.
expansionReleaseYear
chosen
Indicates the year in which an expansion (such as an add-on, DLC, or extended version) is officially released.
-
E.
consoleReleaseYear
Indicates the year in which a particular game console was first released to the public.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.