Triple
T4597887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ping An Insurance |
E100248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial services conglomerate |
C972
|
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: financial services conglomerate Context triple: [Ping An Insurance, instanceOf, financial services conglomerate]
-
A.
financial institution
chosen
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.
-
B.
financial market infrastructure company
A financial market infrastructure company provides the core systems, platforms, and services that enable the trading, clearing, settlement, and reporting of financial instruments in a safe, efficient, and regulated manner.
-
C.
Conglomerate
A conglomerate is a large corporation composed of diverse, often unrelated businesses or subsidiaries managed under a single corporate group.
-
D.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
-
E.
media and telecommunications conglomerate
A media and telecommunications conglomerate is a large corporate entity that owns and operates a diverse portfolio of media, entertainment, and communication businesses across multiple platforms and markets.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.