Triple
T23736349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi territorial waters |
E586550
|
entity |
| Predicate | includeStrait |
P2744
|
FINISHED |
| Object | Strait of Tiran |
—
|
NE NERFINISHED |
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: Strait of Tiran | Statement: [Saudi territorial waters, includeStrait, Strait of Tiran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeStrait Context triple: [Saudi territorial waters, includeStrait, Strait of Tiran]
-
A.
hasStrait
chosen
Indicates that there is a strait—a narrow body of water—connecting or lying between the two referenced geographic entities.
-
B.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
C.
locatedInStrait
Indicates that something is situated within or passes through a narrow body of water (a strait) that connects two larger bodies of water.
-
D.
isNorthernmostStraitOf
Indicates that one strait is the furthest north among all straits associated with a particular geographic feature or region.
-
E.
involvedStrait
Indicates that the entities are connected through, or have a relationship involving, a particular strait (a narrow 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad28fa481909d7a6a6e98a7b0a5 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.