Triple
T5186529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Autobidder |
E117044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | energy trading software platform |
C17783
|
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: energy trading software platform Context triple: [Tesla Autobidder, instanceOf, energy trading software platform]
-
A.
trading consortium
A trading consortium is a collaborative alliance of independent businesses or organizations that pool resources, share information, and coordinate strategies to enhance their collective trading power and market reach.
-
B.
financial settlement platform
A financial settlement platform is a system that facilitates the secure, accurate, and timely clearing and settlement of financial transactions between parties, often integrating payment processing, reconciliation, and reporting functions.
-
C.
public finance instrument
A public finance instrument is a tool or mechanism—such as taxes, bonds, or subsidies—used by governments to raise, allocate, or manage funds for public purposes and policy objectives.
-
D.
agricultural commodities exchange
An agricultural commodities exchange is a marketplace where standardized contracts for buying and selling farm products like grains, livestock, and soft commodities are traded, enabling price discovery, risk management, and efficient distribution.
-
E.
trade expert
A trade expert is a professional who analyzes, advises on, and facilitates domestic and international exchange of goods and services by applying specialized knowledge of markets, regulations, logistics, and negotiation.
- F. None of above. chosen
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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:46 p.m.