Triple
T8393116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Русины |
E197989
|
entity |
| Predicate | языкСтатус |
P25828
|
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.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
B.
languageStatusSource
Indicates the source or authority from which the information about a language’s status is derived.
-
C.
linguisticFeatureStatus
Indicates the current condition or state of a particular linguistic feature (such as whether it is present, active, obsolete, or otherwise characterized) in relation to an entity.
-
D.
officialLanguageStatusSharedWith
Indicates that two entities share at least one official language in common.
-
E.
sociolinguisticStatus
Indicates the social and cultural standing or prestige associated with a language variety or linguistic feature within a particular community or context.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.