Triple
T35502492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Türkmenbaşy oil refinery |
E1026050
|
entity |
| Predicate | exportRoutes |
P61117
|
FINISHED |
| Object | Caspian Sea shipping routes |
—
|
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: Caspian Sea shipping routes | Statement: [Türkmenbaşy oil refinery, exportRoutes, Caspian Sea shipping routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportRoutes Context triple: [Türkmenbaşy oil refinery, exportRoutes, Caspian Sea shipping routes]
-
A.
exportRoute
chosen
Indicates the route or pathway through which goods, services, or data are exported from one location or entity to another.
-
B.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
C.
encodesRoutesIn
Indicates that one entity specifies or defines the routing paths or rules used within another entity.
-
D.
firstRoutes
Indicates that one route or path is the initial or primary route taken or assigned among a set of possible routes.
-
E.
routingSystem
Indicates a relationship where an entity functions as or is associated with a system that determines and manages the paths or routes taken between points.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.