Triple

T15763471
Position Surface form Disambiguated ID Type / Status
Subject Luigi's Mansion: Dark Moon E382154 entity
Predicate regionLock P31533 FINISHED
Object region-locked to 3DS regions 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: region-locked to 3DS regions | Statement: [Luigi's Mansion: Dark Moon, regionLock, region-locked to 3DS regions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionLock
Context triple: [Luigi's Mansion: Dark Moon, regionLock, region-locked to 3DS regions]
  • A. regionLocking chosen
    Indicates that access to or use of something is restricted based on the geographic region of the user or device.
  • B. guardedRegion
    Indicates that a region is protected or watched over by some guarding entity or mechanism.
  • 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. requiresLock
    Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
  • E. lockedMeans
    Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
  • 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_69d86da09a10819082fe9797b23e4664 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b6c9fc8190a1bcf763c4b04b12 completed April 16, 2026, 3 a.m.
PD Predicate disambiguation batch_69e00531e7ac8190a4190cce4f7fab4c completed April 15, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:47 a.m.