Triple
T16904137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania VII |
E424514
|
entity |
| Predicate | mainEventDecision |
P125148
|
FINISHED |
| Object | pinfall |
—
|
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: pinfall | Statement: [WrestleMania VII, mainEventDecision, pinfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventDecision Context triple: [WrestleMania VII, mainEventDecision, pinfall]
-
A.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
B.
mainEventResult
Indicates the outcome or consequence that directly results from the primary event in a given context.
-
C.
mainEventStipulation
Indicates that a specified condition, requirement, or rule must be satisfied for the main event or primary occurrence in a given context.
-
D.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
E.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8de3070819085bfe9696bc887ea |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:30 a.m.