Triple
T35612799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Библиотека имени Ленина |
E1029082
|
entity |
| Predicate | имеетФонд |
P185991
|
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.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
B.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
C.
providedFoundationFor
Indicates that one entity served as the essential basis, support, or groundwork enabling the existence, development, or success of another entity or outcome.
-
D.
isCharityFunded
Indicates that an entity receives financial support or resources from charitable organizations, donations, or philanthropic funding sources.
-
E.
includesFundingFor
Indicates that one entity’s financial resources or budget allocation explicitly cover or provide funding for another entity, project, or activity.
- 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_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:05 p.m.