Triple
T38334060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michelle McCool |
E1037901
|
entity |
| Predicate | appearedInMatchType |
P48257
|
FINISHED |
| Object | Royal Rumble |
—
|
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: Royal Rumble | Statement: [Michelle McCool, appearedInMatchType, Royal Rumble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearedInMatchType Context triple: [Michelle McCool, appearedInMatchType, Royal Rumble]
-
A.
playedInMatch
Indicates that an entity participated as a player in a particular match.
-
B.
attendMatchType
Indicates that an entity participates in or is present at a sports match of a specified type.
-
C.
featuredMatchType
chosen
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
D.
conferenceMatchupType
Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
-
E.
wonMatchType
Indicates that one entity achieved victory in a match of a specified type or category over another 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:30 p.m.