Triple
T18295690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Turkish alphabet |
E438223
|
entity |
| Predicate | usedForPoetry |
P29869
|
FINISHED |
| Object | Divan poetry |
—
|
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: Divan poetry | Statement: [Ottoman Turkish alphabet, usedForPoetry, Divan poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForPoetry Context triple: [Ottoman Turkish alphabet, usedForPoetry, Divan poetry]
-
A.
usedByPoet
Indicates that something (such as a word, style, device, or object) is employed or utilized by a poet.
-
B.
poem
Indicates that one entity is a poem created, authored, or associated with another entity.
-
C.
languageOfPoetry
chosen
Indicates that a specified language is the language in which a given piece of poetry is written or expressed.
-
D.
usesPoetryCollection
Indicates that one entity employs or makes use of a poetry collection in performing an action, fulfilling a function, or supporting some activity or process.
-
E.
poeticCategory
Indicates that one entity is classified as belonging to a particular poetic category or type of poetry in relation to 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017783748190905ce4eeadd25841 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.