Triple
T1218108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Oman |
E26153
|
entity |
| Predicate | seaRouteFor |
P10083
|
FINISHED |
| Object | crude oil exports from Persian Gulf states |
—
|
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: crude oil exports from Persian Gulf states | Statement: [Gulf of Oman, seaRouteFor, crude oil exports from Persian Gulf states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaRouteFor Context triple: [Gulf of Oman, seaRouteFor, crude oil exports from Persian Gulf states]
-
A.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
-
B.
sailingRoute
Indicates a path or course taken by a vessel when traveling by water from one location to another.
-
C.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
D.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
E.
hasMajorSeaLane
chosen
Indicates that a significant maritime shipping or navigation route passes through, borders, or is closely associated with the referenced 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be08157c8190b248bb75b922644f |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.