Triple
T29365800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Çubuklu |
E744713
|
entity |
| Predicate | partOfStraitRegion |
P71311
|
FINISHED |
| Object | Bosphorus strait |
—
|
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: Bosphorus strait | Statement: [Çubuklu, partOfStraitRegion, Bosphorus strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfStraitRegion Context triple: [Çubuklu, partOfStraitRegion, Bosphorus strait]
-
A.
locatedInStrait
chosen
Indicates that something is situated within or passes through a narrow body of water (a strait) that connects two larger bodies of water.
-
B.
isNorthernmostStraitOf
Indicates that one strait is the furthest north among all straits associated with a particular geographic feature or region.
-
C.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
D.
hasStrait
Indicates that there is a strait—a narrow body of water—connecting or lying between the two referenced geographic entities.
-
E.
isMaritimeRegion
Indicates that a region is primarily associated with the sea or ocean, such as being coastal, oceanic, or otherwise defined by maritime characteristics or activities.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 28, 2026, 2:22 p.m.