Triple
T25086921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCW World Tag Team Championship |
E628348
|
entity |
| Predicate | defendedOnEvent |
P109907
|
FINISHED |
| Object | SuperBrawl |
—
|
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: SuperBrawl | Statement: [WCW World Tag Team Championship, defendedOnEvent, SuperBrawl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendedOnEvent Context triple: [WCW World Tag Team Championship, defendedOnEvent, SuperBrawl]
-
A.
defendedAtEvent
chosen
Indicates that an entity (typically a work, thesis, or position) was formally defended or argued for during a specific event.
-
B.
defendedOn
Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
-
C.
defendedOnShow
Indicates that one entity publicly supported or justified another entity during a particular show or broadcast.
-
D.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
E.
defeatedInEvent
Indicates that one entity lost to another entity in the context of a specific event or competition.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:23 a.m.