Triple
T3230175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All for You Tour |
E67718
|
entity |
| Predicate | hasStageDesignElement |
P46313
|
FINISHED |
| Object | multi-level stage |
—
|
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: multi-level stage | Statement: [All for You Tour, hasStageDesignElement, multi-level stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageDesignElement Context triple: [All for You Tour, hasStageDesignElement, multi-level stage]
-
A.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
B.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
requiredDesignElement
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
-
E.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
- F. None of above. chosen
Provenance (4 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb99e088190a8eeca2ca53707e7 |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:08 p.m.