Triple
T4522037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justified and Stripped Tour |
E103289
|
entity |
| Predicate | hasStageDesignStyle |
P35532
|
FINISHED |
| Object | theatrical production |
—
|
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: theatrical production | Statement: [Justified and Stripped Tour, hasStageDesignStyle, theatrical production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageDesignStyle Context triple: [Justified and Stripped Tour, hasStageDesignStyle, theatrical production]
-
A.
hasStageDesignElement
Indicates a relationship in which a stage production, performance, or set includes or is associated with a particular stage design element (such as props, scenery, lighting, or other visual components).
-
B.
hasStepDesign
Indicates that one entity possesses or incorporates a particular step-related design or configuration in relation to another entity.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
stagingStyle
chosen
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574bd6908190b939d92b5809b101 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.