Triple
T19450393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atari Lynx |
E486599
|
entity |
| Predicate | approximateBatteryLife |
P25992
|
FINISHED |
| Object | 4 to 5 hours |
—
|
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: 4 to 5 hours | Statement: [Atari Lynx, approximateBatteryLife, 4 to 5 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateBatteryLife Context triple: [Atari Lynx, approximateBatteryLife, 4 to 5 hours]
-
A.
batteryLife
chosen
Indicates how long a device can operate on a single charge or set of batteries before needing to be recharged or replaced.
-
B.
batteryCapacity
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
C.
powerDuration
Indicates the length of time for which a power, ability, or effect remains active or in force.
-
D.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
E.
hasInternalBattery
Indicates that one entity possesses a built-in power source contained within itself, rather than relying solely on external power.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.