Triple
T6507937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İmroz |
E150057
|
entity |
| Predicate | hasVillage |
P4011
|
FINISHED |
| Object | Kaleköy |
E601891
|
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: Kaleköy | Statement: [İmroz, hasVillage, Kaleköy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaleköy Context triple: [İmroz, hasVillage, Kaleköy]
-
A.
Kalecik
Kalecik is a district and town in central Turkey known for its historic architecture and the locally famous Kalecik Karası grape variety.
-
B.
Karaköy
Karaköy is a historic waterfront neighborhood in Istanbul known for its bustling port, cafes, and mix of traditional and modern urban life.
-
C.
Poyrazköy
Poyrazköy is a coastal neighborhood on the Asian side of Istanbul, Turkey, situated at the northern entrance of the Bosphorus Strait.
-
D.
Dereköy
chosen
Dereköy is a village on the Aegean island of Gökçeada (historically known as Imbros/İmroz) in Turkey, noted for its traditional stone houses and Greek heritage.
-
E.
Hasköy
Hasköy is a historic neighborhood on the European side of Istanbul, known for its multicultural past and its location along the Golden Horn.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c699693d94819088e8adff364e834a |
completed | March 27, 2026, 2:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d50d155c81908b01914db32494d8 |
completed | March 27, 2026, 7:05 p.m. |
Created at: March 27, 2026, 1:43 p.m.