Triple
T26326750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo R&D4 |
E662272
|
entity |
| Predicate | contributedToFranchise |
P83655
|
FINISHED |
| Object | Super Mario |
—
|
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: Super Mario | Statement: [Nintendo R&D4, contributedToFranchise, Super Mario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedToFranchise Context triple: [Nintendo R&D4, contributedToFranchise, Super Mario]
-
A.
franchiseContribution
chosen
Indicates that an entity provides resources, value, or support to a franchise or franchised operation.
-
B.
includedInFranchise
Indicates that an entity is part of, or belongs to, a larger franchise or franchise series.
-
C.
createdForFranchise
Indicates that something was created specifically to belong to, support, or be used within a particular franchise.
-
D.
intendedFranchise
Indicates that one entity is planned or designated to become part of, or operate under, the franchise of another entity.
-
E.
usedByFranchise
Indicates that something (such as a resource, asset, or element) is utilized or employed by a particular franchise.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 10:31 p.m.