Triple
T1775285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Air (M1, 2020) |
E38962
|
entity |
| Predicate | batteryLifeWirelessWeb |
P25992
|
FINISHED |
| Object | up to 15 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 15 hours | Statement: [MacBook Air (M1, 2020), batteryLifeWirelessWeb, up to 15 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryLifeWirelessWeb Context triple: [MacBook Air (M1, 2020), batteryLifeWirelessWeb, up to 15 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.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
C.
wirelessSupportIntroduced
Indicates that support for wireless functionality was added or became available for the first time.
-
D.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.