Triple
T7032869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Classmate PC |
E163310
|
entity |
| Predicate | powerFeature |
P29915
|
FINISHED |
| Object | long battery life relative to cost |
—
|
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: long battery life relative to cost | Statement: [Intel Classmate PC, powerFeature, long battery life relative to cost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerFeature Context triple: [Intel Classmate PC, powerFeature, long battery life relative to cost]
-
A.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
B.
powerChange
Indicates a change in the level, amount, or state of power associated with an entity over time.
-
C.
powerCharacteristic
chosen
Indicates a relationship where one entity has a specific power-related property, capacity, or performance attribute characterized by the other entity.
-
D.
enablingPowerFor
Indicates that one entity provides the capability or authority that allows another entity to perform a specific function, action, or role.
-
E.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.