Triple
T22268773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mophie |
E550418
|
entity |
| Predicate | servesCustomerNeed |
P125614
|
FINISHED |
| Object | extended battery life |
—
|
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: extended battery life | Statement: [Mophie, servesCustomerNeed, extended battery life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCustomerNeed Context triple: [Mophie, servesCustomerNeed, extended battery life]
-
A.
servesCustomer
Indicates that one entity provides service, assistance, or products to another entity in the role of a customer.
-
B.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
-
C.
targetConsumerNeed
chosen
Indicates that something is intended to address, satisfy, or be directed toward a specific need or requirement of a consumer.
-
D.
meetsNeedOf
Indicates that one entity sufficiently fulfills or satisfies the requirement, demand, or expectation specified by another entity.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bde9f88190b533bcb88787b492 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.