Triple
T25999042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen-Edebiyat Fakültesi |
E646567
|
entity |
| Predicate | bulunduğuBölge |
P64798
|
FINISHED |
| Object | Marmara Bölgesi |
—
|
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: Marmara Bölgesi | Statement: [Fen-Edebiyat Fakültesi, bulunduğuBölge, Marmara Bölgesi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bulunduğuBölge Context triple: [Fen-Edebiyat Fakültesi, bulunduğuBölge, Marmara Bölgesi]
-
A.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
B.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
C.
administrativeCenterRegion
Indicates that a region serves as the administrative center or seat of government for another territorial unit.
-
D.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
E.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605720be48190b1b64ecdccfaec17 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:58 a.m.