Triple
T24203881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Rumble |
E600048
|
entity |
| Predicate | usesEntrySystem |
P155183
|
FINISHED |
| Object | interval-based staggered entries |
—
|
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: interval-based staggered entries | Statement: [Royal Rumble, usesEntrySystem, interval-based staggered entries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEntrySystem Context triple: [Royal Rumble, usesEntrySystem, interval-based staggered entries]
-
A.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
-
B.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
C.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
D.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
E.
usesDataSystem
Indicates that one entity employs, accesses, or relies on a particular data system to perform its functions or operations.
- 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.