Triple
T29935103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo Pocket |
E760336
|
entity |
| Predicate | additionalPowerSource |
P137634
|
FINISHED |
| Object | CR2032 backup battery |
—
|
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: CR2032 backup battery | Statement: [Neo Geo Pocket, additionalPowerSource, CR2032 backup battery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalPowerSource Context triple: [Neo Geo Pocket, additionalPowerSource, CR2032 backup battery]
-
A.
backupPowerSource
chosen
Indicates that one entity serves as an alternative or emergency source of power for another entity when the primary power supply is unavailable or insufficient.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
D.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
-
E.
powerAdapter
Indicates that one entity serves as a power adapter, converting or supplying electrical power for another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d413c081908203059402081897 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:20 p.m.