Triple
T26417225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witness: The Tour |
E664129
|
entity |
| Predicate | mainStageDesignTheme |
P137584
|
FINISHED |
| Object | futuristic |
—
|
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: futuristic | Statement: [Witness: The Tour, mainStageDesignTheme, futuristic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStageDesignTheme Context triple: [Witness: The Tour, mainStageDesignTheme, futuristic]
-
A.
canDesignTheme
Indicates that an entity has the capability or permission to create or customize a visual or stylistic theme for another entity or system.
-
B.
coreDesignStyle
chosen
Indicates the primary or defining design style that characterizes an entity’s overall aesthetic or structural approach.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
torchDesignTheme
Indicates that a torch is associated with or characterized by a particular design theme.
-
E.
stairwayTheme
Indicates that something is associated with, characterized by, or thematically centered around a stairway or staircase.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 11:41 p.m.