Triple
T4135612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equifax Inc. |
E85146
|
entity |
| Predicate | clientTypes |
P809
|
FINISHED |
| Object | Financial institutions |
—
|
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: Financial institutions | Statement: [Equifax Inc., clientTypes, Financial institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientTypes Context triple: [Equifax Inc., clientTypes, Financial institutions]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
D.
clientSDKPlatform
Indicates the software platform or environment on which a client-side SDK is designed to run or be used.
-
E.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.