Triple
T35612809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Библиотека имени Ленина |
E1029082
|
entity |
| Predicate | имеетЧитальныеЗалы |
P186410
|
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.
hasCirculationDesk
Indicates that an entity is equipped with or contains a circulation desk, typically used for managing the lending and return of materials.
-
B.
hasLibraryBranch
Indicates that an entity possesses or is associated with one or more library branches as part of its organizational structure or services.
-
C.
library
Indicates that an entity functions as or is associated with a library, typically as a place or system for storing, organizing, and providing access to collections of information resources.
-
D.
hasBorrowingSystem
Indicates that an entity possesses or employs a system or mechanism for borrowing items, resources, or services.
-
E.
isLendingLibrary
Indicates that an entity functions as a library that lends items (such as books or media) to users.
- F. None of above. chosen
Provenance (4 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:05 p.m.