Triple
T35421616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Plains Castle |
E1023809
|
entity |
| Predicate | introducedInGameRegion |
P196563
|
FINISHED |
| Object | Super Mario World (Japan) |
—
|
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 World (Japan) | Statement: [Donut Plains Castle, introducedInGameRegion, Super Mario World (Japan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInGameRegion Context triple: [Donut Plains Castle, introducedInGameRegion, Super Mario World (Japan)]
-
A.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
-
B.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
C.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
D.
hasPrimaryGameRegion
Indicates that an entity is associated with a main or principal geographic region in which a game is released, played, or targeted.
-
E.
gameRegionType
Indicates the type or category of region in which a game or part of a game takes place.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:03 p.m.