Triple
T34154376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tengiz oil field |
E876090
|
entity |
| Predicate | KazMunayGasStake |
P99020
|
FINISHED |
| Object | 20 percent (approximate) |
—
|
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: 20 percent (approximate) | Statement: [Tengiz oil field, KazMunayGasStake, 20 percent (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KazMunayGasStake Context triple: [Tengiz oil field, KazMunayGasStake, 20 percent (approximate)]
-
A.
hasStake
Indicates that one entity holds an interest, share, or involvement—financial, strategic, or otherwise—in another entity or outcome.
-
B.
stakeDrivenBy
Indicates that the stake or interest in something is motivated, influenced, or determined by a specified driving factor or agent.
-
C.
reducedStakeIn
Indicates that one entity has decreased its ownership share or investment interest in another entity compared to a previous level.
-
D.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
E.
ownershipStake
chosen
Indicates that one entity holds a partial or full ownership interest or equity stake in another entity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.