Triple
T13287824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman Divan literature |
E316487
|
entity |
| Predicate | usesLanguageRegister |
P109329
|
FINISHED |
| Object | highly ornate |
—
|
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: highly ornate | Statement: [Ottoman Divan literature, usesLanguageRegister, highly ornate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageRegister Context triple: [Ottoman Divan literature, usesLanguageRegister, highly ornate]
-
A.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
B.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
C.
usesLanguageForAdministration
Indicates that an entity employs a particular language as the official medium for its administrative or governmental functions.
-
D.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
E.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:27 p.m.