Triple
T3532573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian language promotion laws |
E74692
|
entity |
| Predicate | languageTarget |
P21151
|
FINISHED |
| Object | Ukrainian language |
—
|
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 language | Statement: [Ukrainian language promotion laws, languageTarget, Ukrainian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageTarget Context triple: [Ukrainian language promotion laws, languageTarget, Ukrainian language]
-
A.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
B.
translationTargetLanguage
chosen
Indicates the language into which content is being or has been translated.
-
C.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
languagePair
Indicates a relationship that associates two specific languages as a paired combination, typically for translation, comparison, or mapping between them.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9a14c881908932b17ed3eececb |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.