Triple

T11660590
Position Surface form Disambiguated ID Type / Status
Subject Nintendo eShop E277107 entity
Predicate regionLocked P31533 FINISHED
Object true 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: true | Statement: [Nintendo eShop, regionLocked, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionLocked
Context triple: [Nintendo eShop, regionLocked, true]
  • A. regionLocking chosen
    Indicates that access to or use of something is restricted based on the geographic region of the user or device.
  • B. occupiedRegion
    Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
  • C. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • D. regionAtStake
    Indicates that a specific geographic or political area is the subject of contention, risk, or negotiation within a given situation or interaction.
  • E. guardedRegion
    Indicates that a region is protected or watched over by some guarding entity or mechanism.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3d29fdc8190af46b6e2badb1df5 completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d88a73f9ac819095662042804bf40a completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:39 p.m.