Triple
T3008267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE SmackDown |
E81954
|
entity |
| Predicate | usesStorytellingStyle |
P26602
|
FINISHED |
| Object | long-term story arcs |
—
|
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: long-term story arcs | Statement: [WWE SmackDown, usesStorytellingStyle, long-term story arcs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorytellingStyle Context triple: [WWE SmackDown, usesStorytellingStyle, long-term story arcs]
-
A.
usesNarrativeStyle
chosen
Indicates that one entity employs or adopts a particular narrative style in presenting or structuring content or information.
-
B.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
E.
narrativeFormat
Indicates the specific structural or stylistic form in which a narrative is presented or expressed.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ba6988190be29c00cd4266941 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.