Triple
T29100083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola DynaTAC |
E736615
|
entity |
| Predicate | batteryLifeTalkTime |
P103409
|
FINISHED |
| Object | about 30 minutes |
—
|
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: about 30 minutes | Statement: [Motorola DynaTAC, batteryLifeTalkTime, about 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryLifeTalkTime Context triple: [Motorola DynaTAC, batteryLifeTalkTime, about 30 minutes]
-
A.
batteryLife
Indicates how long a device can operate on a single charge or set of batteries before needing to be recharged or replaced.
-
B.
supportsTalkTime
chosen
Indicates that an entity provides or enables a specified duration of talk time for another entity (e.g., a device, plan, or service).
-
C.
batteryCapacity
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
D.
mainBatteryFeature
Indicates the primary functional characteristic or capability associated with a battery.
-
E.
powerCharacteristic
Indicates a relationship where one entity has a specific power-related property, capacity, or performance attribute characterized by the other 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66184e9208190a66378cac527bca9 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:11 a.m.