Triple
T35401655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IndieCommerce |
E1023247
|
entity |
| Predicate | typeOfCustomer |
P809
|
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: [IndieCommerce, typeOfCustomer, small businesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCustomer Context triple: [IndieCommerce, typeOfCustomer, small businesses]
-
A.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
underlyingCompanyCustomerType
Indicates the type or category of customer relationship that an underlying company has (e.g., retail, institutional, corporate).
-
C.
issuerCustomerType
Indicates the type or category of customer associated with or defined by the issuer.
-
D.
personType
Indicates that an entity is classified as a particular type or category of person.
-
E.
accountType
Indicates the specific category or classification of an account within a system or context.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
Created at: May 3, 2026, 4:03 p.m.