Triple
T29963169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DJ BoBo |
E761103
|
entity |
| Predicate | stageShowStyle |
P35532
|
FINISHED |
| Object | elaborate dance and visual productions |
—
|
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: elaborate dance and visual productions | Statement: [DJ BoBo, stageShowStyle, elaborate dance and visual productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageShowStyle Context triple: [DJ BoBo, stageShowStyle, elaborate dance and visual productions]
-
A.
stageAppearanceFeature
Indicates a characteristic or attribute that is present or displayed in an entity’s stage appearance.
-
B.
stageSystem
Indicates a relationship where a system is arranged, set up, or prepared in stages or on a particular stage for operation or presentation.
-
C.
stagingStyle
chosen
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
D.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
E.
stageCostume
Indicates that one entity is a costume specifically used or worn for a performance or stage production 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 6:29 p.m.