Triple
T24204875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lita |
E600076
|
entity |
| Predicate | participatedInMatchType |
P48257
|
FINISHED |
| Object | Royal Rumble match |
—
|
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 match | Statement: [Lita, participatedInMatchType, Royal Rumble match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatedInMatchType Context triple: [Lita, participatedInMatchType, Royal Rumble match]
-
A.
conferenceMatchupType
Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
-
B.
featuredMatchType
chosen
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
C.
tookPlaceInMatch
Indicates that an event or action occurred during a specific match.
-
D.
canBeDefendedInMatchType
Indicates that a particular title, position, or status is eligible to be defended or contested within a specified type of match or competition.
-
E.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.