Triple
T37610791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God Hand |
E935777
|
entity |
| Predicate | notableRegionRelease |
P39809
|
FINISHED |
| Object | Japan |
E174
|
NE 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 | Statement: [God Hand, notableRegionRelease, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegionRelease Context triple: [God Hand, notableRegionRelease, Japan]
-
A.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
B.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
C.
notableCountryOfRelease
Indicates the country where a work was most prominently or significantly released.
-
D.
releaseTitleInSomeRegions
Indicates that a release carries this specific title only in certain geographic regions or markets.
-
E.
regionReleaseDate
Indicates the date on which something is released or becomes available in a specific geographic region.
- F. None of above.
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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afdf21b08190931b6be0f6c105d9 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.