Triple
T17194322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Иронтæй |
E417306
|
entity |
| Predicate | используемыйАлфавит |
P7160
|
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.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
previouslyUsedAlphabet
Indicates that an entity once employed a particular alphabet in the past, but no longer uses it as its current writing system.
-
C.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
D.
alphabetic
Indicates that the characters in a string or sequence consist solely of letters from an alphabet, with no digits or special symbols.
-
E.
используетсяС
Indicates that something is used together with or by means of 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_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.