Triple
T17194405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | осетины |
E417308
|
entity |
| Predicate | раньшеИспользуемаяПисьменность |
P26603
|
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.
writingSystemUsedSince
Indicates that a particular writing system has been in use starting from a specified point in time or period.
-
C.
writingSystemUsedIn
chosen
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
writingSystemDevelopedFrom
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
E.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42da93bf88190b60b658087779d36 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.