Triple
T25059851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extreme Championship Wrestling |
E627625
|
entity |
| Predicate | firstPayPerViewEvent |
P146960
|
FINISHED |
| Object | Barely Legal |
—
|
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: Barely Legal | Statement: [Extreme Championship Wrestling, firstPayPerViewEvent, Barely Legal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPayPerViewEvent Context triple: [Extreme Championship Wrestling, firstPayPerViewEvent, Barely Legal]
-
A.
payPerViewDebut
chosen
Indicates the event or context in which an entity first appears or is introduced on a pay-per-view broadcast.
-
B.
payPerView
Indicates a relationship where access to specific content or an event is granted only upon a one-time payment for that individual viewing.
-
C.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
-
D.
payPerViewDraw
Indicates that an entity attracts or generates audience interest and revenue specifically through pay-per-view events.
-
E.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 18, 2026, 6:09 a.m.