Triple
T7829837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangerous Woman Tour |
E181337
|
entity |
| Predicate | mainStageDesignFeature |
P57584
|
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: [Dangerous Woman Tour, mainStageDesignFeature, large video screens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStageDesignFeature Context triple: [Dangerous Woman Tour, mainStageDesignFeature, large video screens]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
stageDesigner
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
C.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
D.
isMainStageOf
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
E.
featuresDecor
Indicates that one entity includes or showcases the decor elements provided or defined by 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04ac013c81909533fa348776f50c |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.