Triple
T35003866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahçelievler |
E1009755
|
entity |
| Predicate | hasNeighbouringHigherUnit |
P201443
|
FINISHED |
| Object | Karşıyaka district |
E316703
|
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: Karşıyaka district | Statement: [Bahçelievler, hasNeighbouringHigherUnit, Karşıyaka district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringHigherUnit Context triple: [Bahçelievler, hasNeighbouringHigherUnit, Karşıyaka district]
-
A.
hasNeighbouringUnit
Indicates that one unit is directly adjacent to and shares a boundary or side with another unit.
-
B.
hasEvenHigherGeographicUnit
Indicates that one geographic unit is directly contained within or subordinate to another geographic unit at a higher hierarchical level.
-
C.
hasNeighbouringAdministrativeUnitType
Indicates that one administrative unit is directly adjacent to another administrative unit of a specified type.
-
D.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
E.
hasHigherLevelRegion
Indicates that one region is geographically or administratively contained within and subordinate to a larger, higher-level region.
- F. None of above. chosen
Provenance (5 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819c49378819088445c224d3f9f0f |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fff59875cc8190864864e951951679 |
completed | May 10, 2026, 3:03 a.m. |
Created at: May 3, 2026, 4:01 p.m.