Triple
T27879305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slammiversary |
E705042
|
entity |
| Predicate | hasStorylineStructure |
P86551
|
FINISHED |
| Object | culmination of long-term feuds |
—
|
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: culmination of long-term feuds | Statement: [Slammiversary, hasStorylineStructure, culmination of long-term feuds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorylineStructure Context triple: [Slammiversary, hasStorylineStructure, culmination of long-term feuds]
-
A.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
B.
hasDramaticStructure
chosen
Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
-
C.
hasStorylineBuild
Indicates that one element contributes to or defines the development or structure of another element’s storyline.
-
D.
hasChronologicalStructure
Indicates that something is organized or arranged according to the order in which events occur over time.
-
E.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 6:29 p.m.