Triple
T6519348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German National Library |
E148341
|
entity |
| Predicate | legalDeposit |
P14394
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [German National Library, legalDeposit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDeposit Context triple: [German National Library, legalDeposit, yes]
-
A.
legalDepositSince
Indicates that a legal deposit obligation or status has been in effect for the subject entity continuously since the specified date.
-
B.
legalHolding
Indicates that an entity possesses or controls something (such as property, assets, or rights) in a manner recognized and defined by law.
-
C.
hasLegalDeposit
chosen
Indicates that an entity is required to deposit copies of its published material with a designated legal deposit institution or repository.
-
D.
legalCharge
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
-
E.
legalCollection
Indicates that the collection or gathering of something is permitted and conducted in accordance with applicable laws or regulations.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac11d0e481908103c4b51de9521e |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.