Triple
T879333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juhurim |
E18991
|
entity |
| Predicate | languageScript |
P16462
|
FINISHED |
| Object | 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: Cyrillic | Statement: [Juhurim, languageScript, Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageScript Context triple: [Juhurim, languageScript, Cyrillic]
-
A.
languageName
Indicates the specific name assigned to a language in the relationship.
-
B.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
C.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
associatedLanguageScript
chosen
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
E.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acc9d5f4819087afbb75b6ac3dbf |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.