Triple
T31439524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Inn |
E802028
|
entity |
| Predicate | gameReleaseRegion |
P35878
|
FINISHED |
| Object | 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: Japan | Statement: [Rogueport Inn, gameReleaseRegion, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameReleaseRegion Context triple: [Rogueport Inn, gameReleaseRegion, Japan]
-
A.
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.
-
B.
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.
-
C.
releaseRegion
chosen
Indicates the geographic or jurisdictional area in which something (such as a product, service, or content) is made available or officially released.
-
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.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:04 p.m.