Triple
T1136356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosporus |
E23148
|
entity |
| Predicate | hasShoreOn |
P26435
|
FINISHED |
| Object | European side of Istanbul |
—
|
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: European side of Istanbul | Statement: [Bosporus, hasShoreOn, European side of Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoreOn Context triple: [Bosporus, hasShoreOn, European side of Istanbul]
-
A.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
B.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
C.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
D.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
E.
hasSeaAccess
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
- F. None of above. chosen
Provenance (4 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bddfa598819088690e1ab010ba0b |
completed | March 1, 2026, 10:29 p.m. |
Created at: March 1, 2026, 7:44 p.m.