Triple
T23374030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caution World Tour |
E593555
|
entity |
| Predicate | includesVisualElements |
P126424
|
FINISHED |
| Object | video projections |
—
|
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: video projections | Statement: [Caution World Tour, includesVisualElements, video projections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVisualElements Context triple: [Caution World Tour, includesVisualElements, video projections]
-
A.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
B.
hasCommonVisualElement
Indicates that two or more entities share at least one similar or identical visual feature or component.
-
C.
hasVisuals
chosen
Indicates that one entity includes, displays, or is associated with visual elements or imagery related to another entity.
-
D.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
E.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b1d24881909945936cbf00876e |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.