Triple
T26547070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı Devleti Teşkilâtına Medhal |
E671564
|
entity |
| Predicate | başlık |
P38
|
FINISHED |
| Object | Osmanlı Devleti Teşkilâtına Medhal |
—
|
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: Osmanlı Devleti Teşkilâtına Medhal | Statement: [Osmanlı Devleti Teşkilâtına Medhal, başlık, Osmanlı Devleti Teşkilâtına Medhal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: başlık Context triple: [Osmanlı Devleti Teşkilâtına Medhal, başlık, Osmanlı Devleti Teşkilâtına Medhal]
-
A.
title
chosen
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
titleBasis
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
C.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
-
D.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
E.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61436eee08190a23739d9347ec088 |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:45 a.m.