Triple
T37666278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Up, Super Star! |
E937825
|
entity |
| Predicate | associatedWithSeriesEntry |
P119279
|
FINISHED |
| Object | Super Mario Odyssey |
E277105
|
NE 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: Super Mario Odyssey | Statement: [Jump Up, Super Star!, associatedWithSeriesEntry, Super Mario Odyssey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSeriesEntry Context triple: [Jump Up, Super Star!, associatedWithSeriesEntry, Super Mario Odyssey]
-
A.
belongsToSeriesEntry
chosen
Indicates that something is an individual installment or component within a larger series or sequence.
-
B.
associatedWithSeriesSeason
Indicates that an entity is connected or linked to a particular season of a series.
-
C.
associatedWithArtistSeries
Indicates a relationship where something is connected or linked to a particular artist series.
-
D.
associatedCatalogSeries
Indicates that one entity is linked to a catalog series with which it is grouped, classified, or otherwise contextually connected.
-
E.
seriesEntryOf
Indicates that one item functions as an individual entry, installment, or component within a larger series.
- F. None of above.
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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea7347308190bf4a1ef3c836bdda |
completed | June 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.