Triple
T10766808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Petroleum Company |
E253974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | petroleum consortium |
C10923
|
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: petroleum consortium Context triple: [Turkish Petroleum Company, instanceOf, petroleum consortium]
-
A.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
-
B.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
C.
petroleum resources agreement
A petroleum resources agreement is a legally binding contract between a government (or resource owner) and a company (or consortium) that defines the rights, obligations, fiscal terms, and operational conditions for exploring, developing, and producing petroleum resources within a specified area.
-
D.
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.
-
E.
business consortium
chosen
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.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:16 p.m.