Triple
T7931014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LendingClub |
E184187
|
entity |
| Predicate | acquiredCompanyType |
P79839
|
FINISHED |
| Object | online bank |
—
|
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: online bank | Statement: [LendingClub, acquiredCompanyType, online bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredCompanyType Context triple: [LendingClub, acquiredCompanyType, online bank]
-
A.
acquiredCompany
Indicates that one entity has purchased and taken ownership or control of another company.
-
B.
acquisitionType
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
-
C.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
-
D.
backedCompanyType
Indicates the type or category of company that is being financially supported or invested in by another party.
-
E.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
- F. None of above. chosen
Provenance (4 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3accc388819087065ebe7d5d9591 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:07 p.m.