Triple
T10366170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breathe (2017 film) |
E244255
|
entity |
| Predicate | portraysDevice |
P93597
|
FINISHED |
| Object | mechanical ventilator |
—
|
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: mechanical ventilator | Statement: [Breathe (2017 film), portraysDevice, mechanical ventilator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysDevice Context triple: [Breathe (2017 film), portraysDevice, mechanical ventilator]
-
A.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
B.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
C.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
D.
valorDeviceIndicates
Indicates that a Valor device is signaling, reporting, or otherwise providing evidence of a particular state, condition, or event.
-
E.
resolutionDevice
Indicates a device or instrument that is used to resolve, determine, or measure the outcome or value associated with another entity or process.
- F. None of above. chosen
Provenance (4 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96f25f48190a41c8b0206b9238c |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, noon