Triple
T29037963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | reasonForNoAudience |
P34489
|
FINISHED |
| Object | COVID-19 pandemic |
—
|
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: COVID-19 pandemic | Statement: [WrestleMania 36, reasonForNoAudience, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNoAudience Context triple: [WrestleMania 36, reasonForNoAudience, COVID-19 pandemic]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
reasonForNonParticipation
chosen
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
C.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
D.
includesAudienceNoise
Indicates that the event, recording, or media content contains audible sounds from the audience, such as reactions, applause, or background chatter.
-
E.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 10 a.m.