Triple
T28939348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primorsk oil terminal |
E730401
|
entity |
| Predicate | exportRouteFor |
P61117
|
FINISHED |
| Object | Russian western oil export flows |
—
|
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: Russian western oil export flows | Statement: [Primorsk oil terminal, exportRouteFor, Russian western oil export flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportRouteFor Context triple: [Primorsk oil terminal, exportRouteFor, Russian western oil export flows]
-
A.
exportRoute
chosen
Indicates the route or pathway through which goods, services, or data are exported from one location or entity to another.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
exampleRoute
Indicates a route that serves as a representative or illustrative path among possible routes between locations.
-
D.
settingRoute
Indicates that an entity is configuring or defining the path or route to be used for a process, request, or movement.
-
E.
servesAsBaseForRoute
Indicates that one entity functions as the foundational or starting point upon which a route is defined, constructed, or planned.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:35 a.m.