Triple
T30028001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainstage (Tomorrowland) |
E762932
|
entity |
| Predicate | lightingElement |
P1280
|
FINISHED |
| Object | moving head lights |
—
|
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: moving head lights | Statement: [Mainstage (Tomorrowland), lightingElement, moving head lights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingElement Context triple: [Mainstage (Tomorrowland), lightingElement, moving head lights]
-
A.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
B.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
C.
lightingDesigner
Indicates that an entity is responsible for planning, creating, or supervising the lighting design for a production, event, or environment.
-
D.
lightingProvider
Indicates that one entity serves as the source or supplier of lighting for another entity or context.
-
E.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679ad19f88190a01d97605aecb0d8 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:49 p.m.