Triple
T20350347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGB-001 |
E495988
|
entity |
| Predicate | hasBatteryBackupSupport |
P5730
|
FINISHED |
| Object | game save batteries in cartridges |
—
|
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 save batteries in cartridges | Statement: [CGB-001, hasBatteryBackupSupport, game save batteries in cartridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBatteryBackupSupport Context triple: [CGB-001, hasBatteryBackupSupport, game save batteries in cartridges]
-
A.
hasBackupBattery
chosen
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
B.
hasInternalBattery
Indicates that one entity possesses a built-in power source contained within itself, rather than relying solely on external power.
-
C.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
D.
requiresBattery
Indicates that one entity depends on a battery from another entity in order to function or be used.
-
E.
supportsMultipleBatteryCapacities
Indicates that something is designed to work with or accommodate more than one distinct battery capacity option.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6784eacf4819095504e541d1d284d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.