Triple
T2955346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 38 |
E79918
|
entity |
| Predicate | matchTypeNight1MainEvent |
P30656
|
FINISHED |
| Object | No Holds Barred 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: No Holds Barred match | Statement: [WrestleMania 38, matchTypeNight1MainEvent, No Holds Barred match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchTypeNight1MainEvent Context triple: [WrestleMania 38, matchTypeNight1MainEvent, No Holds Barred match]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
finalMatchType
chosen
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
C.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
D.
matingSystem
Indicates the type or pattern of reproductive pairing or mating relationships that typically occurs within a species or population.
-
E.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99286ac8819084f02fbb0a1616d3 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.