Triple
T5072858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowser Jr. Shadow Showdown |
E114320
|
entity |
| Predicate | queueIntegration |
P33920
|
FINISHED |
| Object | Power-Up Band key collection requirement |
—
|
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: Power-Up Band key collection requirement | Statement: [Bowser Jr. Shadow Showdown, queueIntegration, Power-Up Band key collection requirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueIntegration Context triple: [Bowser Jr. Shadow Showdown, queueIntegration, Power-Up Band key collection requirement]
-
A.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
B.
queueLocation
Indicates the place or position where an entity is arranged to wait in a queue or line.
-
C.
hasQueue
chosen
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
D.
integrationEvent
Indicates that one entity participates in or is associated with an event that combines or coordinates multiple components, systems, or processes into a unified whole.
-
E.
borderIntegration
Indicates the degree or manner in which two or more bordering regions are interconnected, coordinated, or functionally unified across their shared boundary.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74cfa4348190bc50590117a6bcf9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.