Triple
T35807990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Cruiserweight Championship |
E1035152
|
entity |
| Predicate | introducedInWWE |
P197071
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [WWE Cruiserweight Championship, introducedInWWE, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInWWE Context triple: [WWE Cruiserweight Championship, introducedInWWE, 2001]
-
A.
wrestlingDebut
Indicates the event or date on which a person first appears in a professional wrestling match or promotion.
-
B.
isFirstWWEPPVMatchFor
Indicates that the referenced match is the first WWE pay-per-view (PPV) match in which the specified participant has competed.
-
C.
activeInWWE
Indicates that a person is currently performing or working as a professional wrestler in World Wrestling Entertainment (WWE).
-
D.
madeWWEDebutAs
Indicates the role, persona, or capacity in which an individual first appeared in WWE.
-
E.
introducedAsAEW&C
Indicates that an entity was introduced or entered into service specifically in the role of an Airborne Early Warning and Control (AEW&C) platform.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69fe7663b5bc81909524c40d3a172512 |
completed | May 8, 2026, 11:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.