Triple
T35805585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jazz |
E1035093
|
entity |
| Predicate | wrestledAtEvent |
P184903
|
FINISHED |
| Object | WrestleMania X8 |
—
|
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: WrestleMania X8 | Statement: [Jazz, wrestledAtEvent, WrestleMania X8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestledAtEvent Context triple: [Jazz, wrestledAtEvent, WrestleMania X8]
-
A.
wrestledFor
Indicates that one entity engaged in a wrestling match or competition on behalf of, or as a representative of, another entity (such as a team, organization, or country).
-
B.
wrestlingEvent
Indicates that a wrestlingEvent relationship holds when an event involves or is characterized by professional or amateur wrestling competition.
-
C.
wrestledForPromotion
Indicates that one entity engaged in a wrestling match or competitive struggle with another in order to gain a promotion or advancement.
-
D.
wrestledOnProgram
Indicates that one entity wrestled on the same program, show, or event as another entity.
-
E.
wrestlingPromotionAppearedIn
Indicates that a wrestler or wrestling-related entity made an appearance in a specific wrestling promotion or organization.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.