Triple
T15073549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Library of Sweden |
E379940
|
entity |
| Predicate | legalDepositFrom |
P4155
|
FINISHED |
| Object | 1661 |
—
|
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: 1661 | Statement: [Royal Library of Sweden, legalDepositFrom, 1661]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDepositFrom Context triple: [Royal Library of Sweden, legalDepositFrom, 1661]
-
A.
legalDepositSince
chosen
Indicates that a legal deposit obligation or status has been in effect for the subject entity continuously since the specified date.
-
B.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
-
C.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
-
D.
legalHolding
Indicates that an entity possesses or controls something (such as property, assets, or rights) in a manner recognized and defined by law.
-
E.
deposes
Indicates the action by which one party forcibly removes another from a position of power or authority.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.