Triple
T12643015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3330 |
E301945
|
entity |
| Predicate | standByTime |
P102822
|
FINISHED |
| Object | up to 260 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 260 hours | Statement: [Nokia 3330, standByTime, up to 260 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standByTime Context triple: [Nokia 3330, standByTime, up to 260 hours]
-
A.
standByTimeClaimed
chosen
Indicates that a standby or waiting time has been reported or asserted for a given entity or event.
-
B.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
D.
sameDayStandbyPolicy
Indicates that a same-day standby policy applies, defining the rules under which an entity can switch to or wait for another option (such as a flight or service) on the same calendar day.
-
E.
maintainsPowerThrough
Indicates that one entity preserves or secures its authority, control, or dominance by means of another entity or specified mechanism.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:17 p.m.