Triple
T30027989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainstage (Tomorrowland) |
E762932
|
entity |
| Predicate | designChanges |
P70881
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [Mainstage (Tomorrowland), designChanges, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designChanges Context triple: [Mainstage (Tomorrowland), designChanges, annually]
-
A.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
B.
hasDesignChange
chosen
Indicates that an entity has undergone a modification or alteration to its original design.
-
C.
decorChanges
Indicates that an entity alters or updates the decorative appearance or arrangement of another entity or environment.
-
D.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
E.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
- 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_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 29, 2026, 6:49 p.m.