Triple
T12620626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дружба народов |
E301368
|
entity |
| Predicate | письменность |
P454
|
FINISHED |
| Object | кириллица |
—
|
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: кириллица | Statement: [Дружба народов, письменность, кириллица]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: письменность Context triple: [Дружба народов, письменность, кириллица]
-
A.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
B.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
D.
דיני כתיבה בו
Indicates that the subject is governed by the same halachic laws and requirements of writing that apply to it (e.g., that the laws of writing are operative in this context).
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.