Triple
T16595193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musandam Governorate |
E403186
|
entity |
| Predicate | partOfStraitShoreline |
P60480
|
FINISHED |
| Object | Omani side of the Strait of Hormuz |
—
|
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: Omani side of the Strait of Hormuz | Statement: [Musandam Governorate, partOfStraitShoreline, Omani side of the Strait of Hormuz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfStraitShoreline Context triple: [Musandam Governorate, partOfStraitShoreline, Omani side of the Strait of Hormuz]
-
A.
isPartOfCoastOf
chosen
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
B.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
C.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
D.
hasHighwayAlongShore
Indicates that a highway runs adjacent to or closely follows the shoreline of a body of water.
-
E.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d717604819083ed60b865bbd13e |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.