Triple
T37666263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Up, Super Star! |
E937825
|
entity |
| Predicate | developerOfAssociatedWork |
P23571
|
FINISHED |
| Object | Nintendo |
—
|
NE NERFINISHED |
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: Nintendo | Statement: [Jump Up, Super Star!, developerOfAssociatedWork, Nintendo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfAssociatedWork Context triple: [Jump Up, Super Star!, developerOfAssociatedWork, Nintendo]
-
A.
developerOfWork
chosen
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
B.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
C.
workProducedBy
Indicates that a particular work (such as a creation, product, or result) was created, generated, or authored by a specific agent or entity.
-
D.
authorOfPreviousWork
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
-
E.
composerOfSourceWork
Indicates that an entity is the composer who created the original source work on which another work is based.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:18 p.m.