Triple
T35394508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iman |
E1023033
|
entity |
| Predicate | gameRegionOfOrigin |
P53696
|
FINISHED |
| Object | Japan-exclusive title |
—
|
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: Japan-exclusive title | Statement: [Iman, gameRegionOfOrigin, Japan-exclusive title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRegionOfOrigin Context triple: [Iman, gameRegionOfOrigin, Japan-exclusive title]
-
A.
hasPrimaryGameRegion
Indicates that an entity is associated with a main or principal geographic region in which a game is released, played, or targeted.
-
B.
homeGroundRegion
Indicates that a sports team’s primary home venue is located within a specified geographic region.
-
C.
countryOfGameOrigin
chosen
Indicates the country where a game was originally created, developed, or first produced.
-
D.
originalPlatformRegion
Indicates the geographic region or market in which a platform was originally launched or made available.
-
E.
releasePlatformRegion
Indicates the specific geographic region or market where a release (such as a product, service, or media title) is made available on a given platform.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.