Triple
T37659538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 7110 |
E937684
|
entity |
| Predicate | approximateStandbyTime |
P126517
|
FINISHED |
| Object | up to 160 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: up to 160 hours | Statement: [Nokia 7110, approximateStandbyTime, up to 160 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateStandbyTime Context triple: [Nokia 7110, approximateStandbyTime, up to 160 hours]
-
A.
standbyTimeMax
chosen
Indicates the maximum duration an entity can remain in standby mode before requiring action, reset, or power.
-
B.
powerDuration
Indicates the length of time for which a power, ability, or effect remains active or in force.
-
C.
standByTimeClaimed
Indicates that a standby or waiting time has been reported or asserted for a given entity or event.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
batteryLife
Indicates how long a device can operate on a single charge or set of batteries before needing to be recharged or replaced.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:18 p.m.