Triple
T8862012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beylerbeyi |
E210912
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Çengelköy |
E640851
|
NE 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: Çengelköy | Statement: [Beylerbeyi, locatedNear, Çengelköy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Çengelköy Context triple: [Beylerbeyi, locatedNear, Çengelköy]
-
A.
Çengelköy
chosen
Çengelköy is a historic neighborhood on Istanbul’s Asian shore of the Bosphorus, known for its waterfront cafes, traditional wooden houses, and scenic views.
-
B.
Çerkezköy
Çerkezköy is an industrial and residential town in northwestern Turkey, located in Tekirdağ Province within the Thrace region.
-
C.
Şirinköy
Şirinköy is a village located on Gökçeada, Turkey’s largest Aegean island in the Çanakkale Province.
-
D.
Yalıköy
Yalıköy is a neighborhood in the Beykoz district of Istanbul, Turkey, known for its residential character and proximity to the Bosphorus.
-
E.
Poyrazköy
Poyrazköy is a coastal neighborhood on the Asian side of Istanbul, Turkey, situated at the northern entrance of the Bosphorus Strait.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc610263048190931bb2c3ac573a08 |
completed | April 1, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfab8fef348190a25e978085e8e656 |
completed | April 3, 2026, 11:59 a.m. |
Created at: March 30, 2026, 6:50 p.m.