Triple
T26849510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmanlı Devleti’nin Kuruluşu |
E676019
|
entity |
| Predicate | akademikStatü |
P161532
|
FINISHED |
| Object | temel başvuru eseri |
—
|
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: temel başvuru eseri | Statement: [Osmanlı Devleti’nin Kuruluşu, akademikStatü, temel başvuru eseri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: akademikStatü Context triple: [Osmanlı Devleti’nin Kuruluşu, akademikStatü, temel başvuru eseri]
-
A.
academicStatus
Indicates the educational or scholarly standing or level an entity holds within an academic context.
-
B.
academicType
Indicates the specific academic category or classification associated with an entity (such as a work, program, or role).
-
C.
hasAcademicRank
Indicates that an entity holds a specific academic rank or title within an educational or research institution.
-
D.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
E.
academicPost
Indicates that an entity holds or is associated with a formal academic position or appointment at an educational or research institution.
- F. None of above. chosen
Provenance (4 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b90393c819090595eac8e538e05 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:15 a.m.