Triple
T30685537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malyn |
E781173
|
entity |
| Predicate | usesAlphabetCountry |
P7160
|
FINISHED |
| Object | Ukrainian Cyrillic |
—
|
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: Ukrainian Cyrillic | Statement: [Malyn, usesAlphabetCountry, Ukrainian Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAlphabetCountry Context triple: [Malyn, usesAlphabetCountry, Ukrainian Cyrillic]
-
A.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
usesAlphabetResources
Indicates that an entity makes use of alphabet-related resources (such as letters, character sets, or alphabet-based tools) in performing an action or function.
-
C.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
D.
useCountry
Indicates that one entity utilizes or operates within the jurisdiction, systems, or context of a specified country.
-
E.
caseCountry
Indicates the country that has legal jurisdiction or is otherwise associated with a particular case.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:33 p.m.