Triple
T3537622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario 64 DS |
E74805
|
entity |
| Predicate | minigamesAccessibleVia |
P29155
|
FINISHED |
| Object | rec room |
—
|
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: rec room | Statement: [Super Mario 64 DS, minigamesAccessibleVia, rec room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minigamesAccessibleVia Context triple: [Super Mario 64 DS, minigamesAccessibleVia, rec room]
-
A.
cityGame6
Indicates a relationship where an entity is associated with a specific city-based game, event, or competition labeled as variant 6.
-
B.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
C.
managedGamesWithAngels
Indicates that a person held a managerial role in baseball games in which the Angels team participated.
-
D.
gamesInBubble
Indicates that the games or matches took place within a controlled or isolated "bubble" environment.
-
E.
relatedGame
chosen
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc928248190b851f8280d58cfcf |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.