Triple
T4135591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equifax Inc. |
E85146
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Consumer credit reporting agency |
C4464
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Consumer credit reporting agency Context triple: [Equifax Inc., instanceOf, Consumer credit reporting agency]
-
A.
credit reporting agency
chosen
A credit reporting agency is an organization that collects, compiles, and provides individuals’ and businesses’ credit information and histories to lenders and other authorized parties to assess creditworthiness.
-
B.
consumer protection agency
A consumer protection agency is a governmental or independent organization that enforces laws and regulations to safeguard consumers from unfair, deceptive, or unsafe business practices.
-
C.
financial institution
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
D.
information services provider
An information services provider is an entity that collects, processes, and delivers data, analysis, or knowledge-based content to users or organizations through various digital or physical channels.
-
E.
merchant cash advance–style product
A merchant cash advance–style product is a financing arrangement where a business receives an upfront lump sum in exchange for a contractually agreed portion of its future sales, typically repaid through automatic deductions from daily or weekly revenue.
- F. None of above.
Provenance (1 batch)
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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:43 p.m.