Triple
T19552558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Can't Dance Tour |
E489228
|
entity |
| Predicate | hasStageProductionFeature |
P182
|
FINISHED |
| Object | large video screens |
—
|
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: large video screens | Statement: [We Can't Dance Tour, hasStageProductionFeature, large video screens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageProductionFeature Context triple: [We Can't Dance Tour, hasStageProductionFeature, large video screens]
-
A.
hasStageProduction
Indicates that one entity is realized, adapted, or presented as a stage production (such as a play, musical, or theatrical performance) associated with another entity.
-
B.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
hasProductionStandard
Indicates that something is governed, defined, or evaluated according to a specific production standard.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d315c68819087402802d624a8c9 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.