Triple
T15648194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamburg gas field |
E376235
|
entity |
| Predicate | exportRole |
P119599
|
FINISHED |
| Object | supplies gas for export to Europe |
—
|
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: supplies gas for export to Europe | Statement: [Yamburg gas field, exportRole, supplies gas for export to Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportRole Context triple: [Yamburg gas field, exportRole, supplies gas for export to Europe]
-
A.
assignsRoleTo
Indicates that one entity designates or grants a specific role or position to another entity.
-
B.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
C.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
D.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
- F. None of above. chosen
Provenance (4 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.