Triple
T34867568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What the Bleep Do We Know!? |
E1005054
|
entity |
| Predicate | usesComputerGraphics |
P98667
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [What the Bleep Do We Know!?, usesComputerGraphics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesComputerGraphics Context triple: [What the Bleep Do We Know!?, usesComputerGraphics, yes]
-
A.
usesComputerAnimationFor
Indicates that something employs computer-generated animation techniques to create or enhance its visual content or effects.
-
B.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
C.
has3DGraphics
chosen
Indicates that something includes or supports three-dimensional graphical representation or rendering.
-
D.
usedInComputerFamily
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
-
E.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
- 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_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4 p.m.