Triple
T28383191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You've Been Framed! |
E718940
|
entity |
| Predicate | clipAcquisitionMethod |
P21736
|
FINISHED |
| Object | viewer submissions |
—
|
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: viewer submissions | Statement: [You've Been Framed!, clipAcquisitionMethod, viewer submissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clipAcquisitionMethod Context triple: [You've Been Framed!, clipAcquisitionMethod, viewer submissions]
-
A.
acquisitionMode
Indicates the method or process by which one entity obtains, receives, or gains another entity or resource.
-
B.
sampleAcquisitionDevice
Indicates the device or instrument used to obtain or collect the sample.
-
C.
captureType
chosen
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
-
D.
acquisitionPattern
Indicates the characteristic way in which one entity acquires or obtains another entity or resource, such as the method, frequency, or structure of the acquisition.
-
E.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb8054c8190a12bc4f58e7e4a61 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:08 a.m.