Triple
T24203856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Rumble |
E600048
|
entity |
| Predicate | hasSignatureMatchType |
P155182
|
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: [Royal Rumble, hasSignatureMatchType, Royal Rumble match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureMatchType Context triple: [Royal Rumble, hasSignatureMatchType, Royal Rumble match]
-
A.
isSignatureHitFor
Indicates that one event, action, or data pattern matches and triggers a specific predefined signature (such as a rule, template, or detection pattern).
-
B.
isSignatureHitOf
Indicates that one hit or impact is the characteristic or defining strike associated with a particular entity, event, or performance.
-
C.
hasSignatureTrait
Indicates that an entity possesses a defining or characteristic trait that is especially distinctive or representative of it.
-
D.
hasSignatureStatusFor
Indicates that a specific entity holds or is assigned a particular signature-related status in relation to another entity or context.
-
E.
hasSignatureBit
Indicates that an entity possesses a specific bit or flag used to represent a signature or signed status in a data structure or encoding.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:37 p.m.