Triple
T29957767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lotus Stage |
E760952
|
entity |
| Predicate | visualSystem |
P135246
|
FINISHED |
| Object | synchronized visuals |
—
|
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: synchronized visuals | Statement: [The Lotus Stage, visualSystem, synchronized visuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualSystem Context triple: [The Lotus Stage, visualSystem, synchronized visuals]
-
A.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
B.
visualExperience
Indicates a relationship where an entity undergoes or has a particular experience involving visual perception or seeing.
-
C.
vision
Indicates that an entity perceives another entity or object visually, using sight.
-
D.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
visualDevice
chosen
Indicates a relationship where an entity functions as or is associated with a device used for visual display, capture, or processing.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:27 p.m.