Triple
T24008830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brad Allen |
E594466
|
entity |
| Predicate | usesTelephoneAsPlotDeviceIn |
P145083
|
FINISHED |
| Object | Pillow Talk |
—
|
NE NERFINISHED |
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: Pillow Talk | Statement: [Brad Allen, usesTelephoneAsPlotDeviceIn, Pillow Talk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTelephoneAsPlotDeviceIn Context triple: [Brad Allen, usesTelephoneAsPlotDeviceIn, Pillow Talk]
-
A.
usesTelecommunications
Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
-
B.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
C.
usesEmergencyNumber
Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
-
D.
usesTechnologyInStory
chosen
Indicates that an entity incorporates or employs a particular technology within the context of a narrative or story.
-
E.
centralPlotDevice
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46c77f88190806e6287e55c9136 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.