Triple
T13242748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SmackDown Women’s Championship |
E315320
|
entity |
| Predicate | contestedOn |
P104078
|
FINISHED |
| Object | WWE pay-per-view events |
—
|
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: WWE pay-per-view events | Statement: [SmackDown Women’s Championship, contestedOn, WWE pay-per-view events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedOn Context triple: [SmackDown Women’s Championship, contestedOn, WWE pay-per-view events]
-
A.
contestedAt
Indicates that an event, claim, or outcome is being challenged or disputed at a particular time or place.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
laterContestedBy
Indicates that an earlier claim, decision, or statement is subsequently challenged or disputed by another party or source.
-
D.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
E.
titleContestedIn
chosen
Indicates that a particular title or championship is being challenged or competed for within a specific event, match, or context.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.