Triple
T5270089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DS |
E119234
|
entity |
| Predicate | secondaryStorage |
P62732
|
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: [Nintendo DS, secondaryStorage, Game Boy Advance cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryStorage Context triple: [Nintendo DS, secondaryStorage, Game Boy Advance cartridge]
-
A.
secondVolume
Indicates that one entity is the second volume or installment in a multi-volume work or series relative to another entity.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryState
Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
-
D.
secondaryAccessMode
Indicates an additional, non-primary way in which an entity can be accessed, used, or interacted with.
-
E.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7d5906d88190b805977e5a05767a |
completed | March 20, 2026, 5:01 p.m. |
Created at: March 20, 2026, 1:51 p.m.