Triple
T35842614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Ring 2001 |
E1036124
|
entity |
| Predicate | tournamentFinalMatch |
P167063
|
FINISHED |
| Object | Edge vs Kurt Angle |
—
|
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: Edge vs Kurt Angle | Statement: [King of the Ring 2001, tournamentFinalMatch, Edge vs Kurt Angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentFinalMatch Context triple: [King of the Ring 2001, tournamentFinalMatch, Edge vs Kurt Angle]
-
A.
tournamentFinalMethod
Indicates the method or format by which the final round or match of a tournament is conducted or decided.
-
B.
finalCompetitiveMatch
chosen
Indicates that a given match is the last or concluding competitive contest for the involved participant(s) or team(s).
-
C.
finalOfficialMatch
Indicates that a given match is the last officially recognized contest or game in a defined series, season, tournament, or career.
-
D.
finalTournamentStage
Indicates that an event or match represents the concluding or championship stage of a tournament.
-
E.
divisionFinalsMatchup
Indicates a competitive pairing between two entities in the final round of a division-level contest or tournament.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.