Triple
T27660713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LendingClub Corporation |
E697112
|
entity |
| Predicate | primaryClientType |
P112711
|
FINISHED |
| Object | individual borrowers |
—
|
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: individual borrowers | Statement: [LendingClub Corporation, primaryClientType, individual borrowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryClientType Context triple: [LendingClub Corporation, primaryClientType, individual borrowers]
-
A.
primaryClient
Indicates that one entity serves as the main or most important client associated with another entity.
-
B.
primaryUserType
Indicates the main or dominant category of user associated with an entity or interaction.
-
C.
primaryClientGroup
chosen
Indicates the main group of clients that an entity primarily serves or is chiefly associated with.
-
D.
primaryPatientType
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
-
E.
primaryVisitorsType
Indicates the main category or type of visitors that predominantly engage with or are targeted by an 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: April 27, 2026, 2:36 p.m.