Triple
T32466304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Cory |
E829716
|
entity |
| Predicate | controlsDevice |
P171744
|
FINISHED |
| Object | life-support apparatus for Donovan's brain |
—
|
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: life-support apparatus for Donovan's brain | Statement: [Patrick Cory, controlsDevice, life-support apparatus for Donovan's brain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsDevice Context triple: [Patrick Cory, controlsDevice, life-support apparatus for Donovan's brain]
-
A.
controlsDeviceType
Indicates that an entity has authority over or can operate a specific type or category of device.
-
B.
controlDeviceTypical
chosen
Indicates that an entity typically operates or manages the functioning of a device.
-
C.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
D.
controlFeatures
Indicates that one entity has the ability to configure, manage, or influence the operational settings or characteristics of another entity.
-
E.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 12:57 a.m.