Triple
T30554190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMX Bandits |
E777648
|
entity |
| Predicate | usesDeviceInPlot |
P9919
|
FINISHED |
| Object | police walkie-talkies |
—
|
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: police walkie-talkies | Statement: [BMX Bandits, usesDeviceInPlot, police walkie-talkies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDeviceInPlot Context triple: [BMX Bandits, usesDeviceInPlot, police walkie-talkies]
-
A.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
B.
supportsPlotDevice
Indicates that one entity provides narrative justification, reinforcement, or facilitation for the use or effectiveness of a particular plot device in a story.
-
C.
relationshipToPlotDevice
Indicates how an entity is functionally or narratively connected to a specific plot device within a story.
-
D.
occursInDevice
Indicates that an event, process, or phenomenon takes place within or inside a specified device.
-
E.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:20 p.m.