Triple
T15537125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii optical disc |
E370375
|
entity |
| Predicate | supportsRegionLocking |
P21828
|
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: [Wii optical disc, supportsRegionLocking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegionLocking Context triple: [Wii optical disc, supportsRegionLocking, true]
-
A.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
-
B.
requiresLock
Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
-
C.
supportsRegionRestriction
chosen
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
D.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by another entity.
-
E.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.