Triple
T27739985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebellion |
E701825
|
entity |
| Predicate | hasStorylineBuild |
P190045
|
FINISHED |
| Object | Impact Wrestling television programs |
—
|
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: Impact Wrestling television programs | Statement: [Rebellion, hasStorylineBuild, Impact Wrestling television programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorylineBuild Context triple: [Rebellion, hasStorylineBuild, Impact Wrestling television programs]
-
A.
hasStorylineType
Indicates that an entity’s storyline belongs to or is categorized under a specific type or narrative classification.
-
B.
hasModernDayStoryline
Indicates that the work’s narrative is set in, or primarily takes place during, contemporary or present-day times.
-
C.
hasBuild
Indicates that one entity has constructed, created, or assembled another entity.
-
D.
hasZoneStoryline
Indicates that a zone or area is associated with a specific overarching storyline or narrative arc.
-
E.
storyboardedBy
Indicates that a visual narrative work (such as a film, animation, or sequence) has its scenes or shots planned and illustrated by a specific storyboard artist or creator.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 27, 2026, 4:09 p.m.