Triple
T34900478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyro: Attack of the Rhynocs |
E1006570
|
entity |
| Predicate | hasRegionLock |
P205600
|
FINISHED |
| Object | Game Boy Advance cartridge |
—
|
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: Game Boy Advance cartridge | Statement: [Spyro: Attack of the Rhynocs, hasRegionLock, Game Boy Advance cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionLock Context triple: [Spyro: Attack of the Rhynocs, hasRegionLock, Game Boy Advance cartridge]
-
A.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
B.
hasLockOperation
Indicates that an entity is associated with a specific lock-related operation, such as locking, unlocking, or otherwise controlling access.
-
C.
hasRegionKey
Indicates that an entity is associated with a specific region through a unique identifying key.
-
D.
hasLocksAt
Indicates that one entity possesses or provides locks that are located at or associated with a specific place or position of another entity.
-
E.
hasLockKeeper
Indicates that an entity is associated with or managed by a specific lock keeper (e.g., the person responsible for operating or overseeing a lock).
- F. None of above. chosen
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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.