Triple
T25364924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flux (Jen Lewin installation) |
E636073
|
entity |
| Predicate | movementDetection |
P158470
|
FINISHED |
| Object | responds to viewers’ movements |
—
|
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: responds to viewers’ movements | Statement: [Flux (Jen Lewin installation), movementDetection, responds to viewers’ movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementDetection Context triple: [Flux (Jen Lewin installation), movementDetection, responds to viewers’ movements]
-
A.
movementDetectedBy
chosen
Indicates that a movement event is sensed or registered by a particular detecting entity or device.
-
B.
binaryDetectionMethod
Indicates a method or technique used to detect or distinguish between two possible states, conditions, or outcomes.
-
C.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10ce1a8819081abc0012ddfaee7 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:36 p.m.