Triple
T35394567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mama |
E1023035
|
entity |
| Predicate | targetPlatformRegion |
P163863
|
FINISHED |
| Object | Japanese market |
—
|
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: Japanese market | Statement: [Mama, targetPlatformRegion, Japanese market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlatformRegion Context triple: [Mama, targetPlatformRegion, Japanese market]
-
A.
originalPlatformRegion
Indicates the geographic region or market in which a platform was originally launched or made available.
-
B.
releasePlatformRegion
chosen
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.
-
C.
endpointRegion
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
-
D.
hasRegionalPlatforms
Indicates that an entity operates or is associated with specific platforms that are organized or deployed at a regional level.
-
E.
launchSiteRegion
Indicates the geographic region in which a launch site is located.
- 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_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:03 p.m.