Triple
T375500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Library |
E8363
|
entity |
| Predicate | legalDepositStatusSince |
P4155
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [British Library, legalDepositStatusSince, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDepositStatusSince Context triple: [British Library, legalDepositStatusSince, 1973]
-
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.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
-
C.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
D.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
E.
closingDoxology
Indicates the concluding liturgical or devotional formula of praise that formally ends a prayer, hymn, or religious text.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec1585648190943f1c698e9b2d81 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96216048190873ae533fa5b864d |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.