Triple
T26579804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. Ride & Go Seek! |
E667045
|
entity |
| Predicate | usesLightingEffect |
P69537
|
FINISHED |
| Object | blacklight effects |
—
|
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: blacklight effects | Statement: [Monsters, Inc. Ride & Go Seek!, usesLightingEffect, blacklight effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLightingEffect Context triple: [Monsters, Inc. Ride & Go Seek!, usesLightingEffect, blacklight effects]
-
A.
hasLightingEffect
chosen
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
-
B.
usesLightingFor
Indicates that one entity employs or relies on a particular lighting setup, technology, or condition to achieve a purpose or perform an action.
-
C.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
visualEffect
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
E.
usesStageEffects
Indicates that an entity employs stage-based visual, auditory, or mechanical effects as part of a performance or presentation.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:02 a.m.