Triple
T3437250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 35 |
E72482
|
entity |
| Predicate | mainEventType |
P7504
|
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: [WrestleMania 35, mainEventType, triple threat match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventType Context triple: [WrestleMania 35, mainEventType, triple threat match]
-
A.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
B.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
C.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
D.
typeOfEvent
chosen
Indicates that one entity is classified as a specific kind or category of event.
-
E.
numberOfMainEvents
Indicates the total count of primary or most significant events associated with a given entity 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f4398c8190a75822068308037b |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.