Triple
T24405751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Deeds |
E615304
|
entity |
| Predicate | usedInStorylinesWith |
P6829
|
FINISHED |
| Object | Seth Rollins |
—
|
NE NERFINISHED |
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: Seth Rollins | Statement: [Dirty Deeds, usedInStorylinesWith, Seth Rollins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInStorylinesWith Context triple: [Dirty Deeds, usedInStorylinesWith, Seth Rollins]
-
A.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
B.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
C.
alsoUsedIn
chosen
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
knownForStoryline
Indicates that an entity is recognized or notable specifically for its narrative or storyline.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dfd8d88190b831b6a8f4157980 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.