Triple
T2893221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Slavs |
E63874
|
entity |
| Predicate | linguisticMembers |
P7390
|
FINISHED |
| Object | Russian 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: Russian language | Statement: [East Slavs, linguisticMembers, Russian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticMembers Context triple: [East Slavs, linguisticMembers, Russian language]
-
A.
hasMemberLanguage
chosen
Indicates that one entity is a language that is a constituent or member of a larger language group, family, or collection represented by the other entity.
-
B.
linguisticRegister
Indicates the level of formality or stylistic variety in which a linguistic expression is typically used within a given context.
-
C.
macrolanguageMemberOf
Indicates that a language variety is classified as a member of a larger macrolanguage grouping.
-
D.
linguisticSubgroup
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
E.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe062234c81909411e34db7d2683d |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:07 p.m.