Triple
T9301897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easyOffice |
E223782
|
entity |
| Predicate | hasTargetCustomers |
P33576
|
FINISHED |
| Object | small businesses |
—
|
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: small businesses | Statement: [easyOffice, hasTargetCustomers, small businesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetCustomers Context triple: [easyOffice, hasTargetCustomers, small businesses]
-
A.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
C.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
hasTargetAudienceRegion
Indicates that something is intended for or directed toward an audience located in a specific geographic region.
-
E.
hasCustomerServices
Indicates that an entity provides or is associated with one or more customer service functions or offerings.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d34c4c819095a213360747c3a6 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.