Triple
T4534518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi Metro Rail Corporation |
E106374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint venture company |
C423
|
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: joint venture company Context triple: [Delhi Metro Rail Corporation, instanceOf, joint venture company]
-
A.
automotive joint venture
An automotive joint venture is a strategic business arrangement in which two or more companies collaborate to develop, produce, or distribute vehicles or related technologies while sharing resources, risks, and profits.
-
B.
corporate venture arm
A corporate venture arm is a dedicated investment unit within a company that funds and partners with startups to access innovation, strategic insights, and new growth opportunities aligned with the parent firm's objectives.
-
C.
business consortium
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
-
D.
company
chosen
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
E.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.