Triple
T9912962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Color – Season of Light |
E185790
|
entity |
| Predicate | showEnvironment |
P853
|
FINISHED |
| Object | outdoor |
—
|
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: outdoor | Statement: [World of Color – Season of Light, showEnvironment, outdoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showEnvironment Context triple: [World of Color – Season of Light, showEnvironment, outdoor]
-
A.
displayEnvironment
Indicates that an entity presents or renders a particular environment or environmental setting for viewing or interaction.
-
B.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
C.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
D.
desktopEnvironment
Indicates that one entity functions as the desktop environment (graphical user interface layer) used or provided by another entity.
-
E.
showType
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53a300481909d917e487d8aab56 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.