Triple
T38570065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleaver |
E929239
|
entity |
| Predicate | usedAsDeviceBy |
P196801
|
FINISHED |
| Object | David Chase |
—
|
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: David Chase | Statement: [Cleaver, usedAsDeviceBy, David Chase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDeviceBy Context triple: [Cleaver, usedAsDeviceBy, David Chase]
-
A.
usedAsDeviceFor
Indicates that one entity functions as a tool, instrument, or device for performing an action or achieving a particular purpose for another entity.
-
B.
usedAsDevice
chosen
Indicates that one entity functions as a device or tool for another entity or purpose.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
-
E.
usedInDeviceFamily
Indicates that something (such as a component, technology, or feature) is employed or incorporated within a particular family of related devices.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:32 p.m.