Triple
T26547174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı Devleti’nin İlmiye Teşkilâtı |
E671566
|
entity |
| Predicate | kapsam |
P160622
|
FINISHED |
| Object | klasik dönem Osmanlı teşkilatı |
—
|
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: klasik dönem Osmanlı teşkilatı | Statement: [Osmanlı Devleti’nin İlmiye Teşkilâtı, kapsam, klasik dönem Osmanlı teşkilatı]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kapsam Context triple: [Osmanlı Devleti’nin İlmiye Teşkilâtı, kapsam, klasik dönem Osmanlı teşkilatı]
-
A.
kapsam
chosen
Indicates that one entity includes, covers, or encompasses another within its scope or range.
-
B.
kapkapRepresents
Indicates that one entity serves as a symbolic or conceptual representation of another entity within a specific context.
-
C.
capsule
Indicates that one entity is a capsule containing, enclosing, or encapsulating another entity.
-
D.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
-
E.
pakad
Indicates the act of catching, holding, or seizing someone or something, typically by grasping or capturing it.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:45 a.m.