Triple
T26137619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Kurdish |
E659424
|
entity |
| Predicate | usedInWritingFor |
P169228
|
FINISHED |
| Object | education |
—
|
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: education | Statement: [Central Kurdish, usedInWritingFor, education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInWritingFor Context triple: [Central Kurdish, usedInWritingFor, education]
-
A.
usedInWriting
Indicates that something (such as a tool, material, or medium) is employed as part of the process or act of writing.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
D.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
E.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 26, 2026, 8:18 p.m.