Triple
T8521428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Pro 13-inch (M1) |
E201700
|
entity |
| Predicate | batteryLifeWirelessWebHours |
P25992
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [MacBook Pro 13-inch (M1), batteryLifeWirelessWebHours, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryLifeWirelessWebHours Context triple: [MacBook Pro 13-inch (M1), batteryLifeWirelessWebHours, 17]
-
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.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
C.
airPowerUsedBy
Indicates that a particular actor employs or deploys air power (such as aircraft or aerial operations) as part of its activities or capabilities.
-
D.
wifiAvailable
Indicates that a location, device, or context has access to a functioning Wi-Fi network.
-
E.
requiresBattery
Indicates that one entity depends on a battery from another entity in order to function or be used.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.