Triple
T25999039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen-Edebiyat Fakültesi |
E646567
|
entity |
| Predicate | kurumOdağı |
P159865
|
FINISHED |
| Object | lisans eğitimi |
—
|
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: lisans eğitimi | Statement: [Fen-Edebiyat Fakültesi, kurumOdağı, lisans eğitimi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kurumOdağı Context triple: [Fen-Edebiyat Fakültesi, kurumOdağı, lisans eğitimi]
-
A.
kurumOdağı
chosen
Indicates a focus on or orientation toward an institution, organization, or corporate entity in the context of the described relationship or action.
-
B.
kokudaka
Indicates a relationship where a landholding or domain is assigned a value based on its assessed agricultural productivity or tax yield, typically measured in koku.
-
C.
kapsam
Indicates that one entity includes, covers, or encompasses another within its scope or range.
-
D.
odakKonu
Indicates a focus-on relationship where one entity is the main subject or topic that another entity concentrates on or addresses.
-
E.
KaumodakiOf
Indicates that one entity is the Kaumodaki (the specific mace/weapon) associated with, possessed by, or emblematic of another entity.
- 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_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:58 a.m.