Triple
T35612816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Библиотека имени Ленина |
E1029082
|
entity |
| Predicate | языкОсновногоФонда |
P18404
|
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.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
-
B.
isWorkingLanguageOf
chosen
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
C.
governingLanguage
Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
-
D.
capitalLanguage
Indicates that the specified language is the primary or official language used in the capital city of a given entity.
-
E.
macrolanguageOf
Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ecbd7dc8190ad5a206b51394814 |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.