Triple
T34867535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What the Bleep Do We Know!? |
E1005054
|
entity |
| Predicate | hasInterviewComponent |
P99527
|
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!?, hasInterviewComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterviewComponent Context triple: [What the Bleep Do We Know!?, hasInterviewComponent, yes]
-
A.
hasInterviews
chosen
Indicates that one entity conducts, contains, or is associated with interviews involving another entity.
-
B.
usesInterviews
Indicates that one entity employs interviews as a method or tool in relation to another entity or process.
-
C.
hasGivenInterviewsIn
Indicates that an entity has conducted or participated in interviews within a specified place or context.
-
D.
hasAuthorInterviewRole
Indicates that an entity participates in an interview in the role of an author.
-
E.
requiresInterview
Indicates that one entity can only proceed, be accepted, or be granted by another entity if an interview is conducted.
- 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_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4 p.m.