Triple
T38228202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storyteller Tour: Stories in the Round |
E1012208
|
entity |
| Predicate | formatEmphasis |
P17414
|
FINISHED |
| Object | story-focused concert experience |
—
|
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: story-focused concert experience | Statement: [Storyteller Tour: Stories in the Round, formatEmphasis, story-focused concert experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatEmphasis Context triple: [Storyteller Tour: Stories in the Round, formatEmphasis, story-focused concert experience]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
matchTypeEmphasis
Indicates that one entity emphasizes or highlights a particular type or category of match in relation to another entity.
-
C.
accentStyle
Indicates the manner or pattern in which an entity’s accent or emphasis is applied or presented.
-
D.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
E.
capitalizationFocus
Indicates a relationship where attention or emphasis is placed on the use, style, or correctness of capitalization in text.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:30 p.m.