Triple
T3741999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 32 |
E79721
|
entity |
| Predicate | intercontinentalTitleMatch |
P51202
|
FINISHED |
| Object | seven-man ladder 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: seven-man ladder match | Statement: [WrestleMania 32, intercontinentalTitleMatch, seven-man ladder match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intercontinentalTitleMatch Context triple: [WrestleMania 32, intercontinentalTitleMatch, seven-man ladder match]
-
A.
intercontinental
Indicates a relationship or action that spans or connects multiple continents.
-
B.
isWorldChampionshipFight
Indicates that a given fight is officially recognized as a world championship bout for a title in its sport.
-
C.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
D.
continentalTitle
Indicates that a title or championship is recognized at the level of an entire continent rather than a national or global scope.
-
E.
internationalTitle
Indicates that an entity has a title or name used in international or cross-border contexts, distinct from its local or original title.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb563fac8190b6a55580d0386e8a |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.