Triple
T35612810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Библиотека имени Ленина |
E1029082
|
entity |
| Predicate | имеетЭлектронныйКаталог |
P9162
|
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.
hasOnlineCatalog
chosen
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
B.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific catalogue.
-
C.
hasExhibitionCatalogue
Indicates that an exhibition is associated with a specific catalogue documenting or describing it.
-
D.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
E.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:05 p.m.