Triple
T31110425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nexus |
E792927
|
entity |
| Predicate | storylineReason |
P175381
|
FINISHED |
| Object | revolt of NXT rookies against WWE management |
—
|
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: revolt of NXT rookies against WWE management | Statement: [The Nexus, storylineReason, revolt of NXT rookies against WWE management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storylineReason Context triple: [The Nexus, storylineReason, revolt of NXT rookies against WWE management]
-
A.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
storylineRelative
Indicates that one narrative element is positioned in relation to another within a storyline, such as in sequence, importance, or structural role.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
E.
storylinesInclude
Indicates that certain storylines are contained within, or form part of, a larger narrative or collection of narratives.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 9:04 p.m.