Triple
T25999030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen-Edebiyat Fakültesi |
E646567
|
entity |
| Predicate | eğitimAlanı |
P126649
|
FINISHED |
| Object | beşeri bilimler |
—
|
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: beşeri bilimler | Statement: [Fen-Edebiyat Fakültesi, eğitimAlanı, beşeri bilimler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eğitimAlanı Context triple: [Fen-Edebiyat Fakültesi, eğitimAlanı, beşeri bilimler]
-
A.
educationalField
chosen
Indicates the academic or disciplinary area in which an educational activity, program, or qualification is focused.
-
B.
educationalSector
Indicates a relationship in which something is part of, associated with, or operates within the education or schooling domain.
-
C.
educationCategory
Indicates the classification of an educational program, content, or activity into a specific type or category based on its subject, level, or purpose.
-
D.
освіта
Indicates that one entity provides, has, or is associated with the education or educational background of another entity.
-
E.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
- 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_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:58 a.m.