Triple
T9616332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ImageWorks: The What-If Labs |
E232227
|
entity |
| Predicate | targetSense |
P89270
|
FINISHED |
| Object | sight |
—
|
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: sight | Statement: [ImageWorks: The What-If Labs, targetSense, sight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSense Context triple: [ImageWorks: The What-If Labs, targetSense, sight]
-
A.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
D.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aad71a0819084ea00c2409e9922 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:09 p.m.