Triple
T35203677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Raw Women’s Championship |
E1016476
|
entity |
| Predicate | firstChampionMatchType |
P184195
|
FINISHED |
| Object | triple threat match |
—
|
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: triple threat match | Statement: [WWE Raw Women’s Championship, firstChampionMatchType, triple threat match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChampionMatchType Context triple: [WWE Raw Women’s Championship, firstChampionMatchType, triple threat match]
-
A.
firstChampion
Indicates that one entity is the earliest or original champion or title-holder in relation to another entity.
-
B.
championWins
Indicates that a champion emerges victorious in a competition, match, or contest.
-
C.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
D.
firstMatchCompetition
Indicates that the referenced competition is the first one in which the entities faced each other or were matched against one another.
-
E.
matchTypeDebut
chosen
Indicates that an entity’s first appearance or participation occurred in a specific type or category of match.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.