Triple
T15384521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wario Stadium |
E367883
|
entity |
| Predicate | hasShortcutGlitches |
P118550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wario Stadium, hasShortcutGlitches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortcutGlitches Context triple: [Wario Stadium, hasShortcutGlitches, yes]
-
A.
hasCheatCodes
Indicates that a game or system includes special codes or commands that allow users to bypass normal rules or gain advantages.
-
B.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
C.
hasSlowCorners
Indicates that an entity possesses corners or turning points that are navigated or traversed at a relatively low speed.
-
D.
hasComplication
Indicates that an entity is associated with a problem, difficulty, or adverse outcome arising as a consequence of another condition, action, or process.
-
E.
hasShortGameArea
Indicates that an entity includes or is associated with a designated short-game practice area (e.g., for chipping, pitching, or putting).
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.