Triple
T30846885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oswald Jonas Memorial Collection |
E785659
|
entity |
| Predicate | hasArchivalLevel |
P66614
|
FINISHED |
| Object | fonds |
—
|
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: fonds | Statement: [Oswald Jonas Memorial Collection, hasArchivalLevel, fonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchivalLevel Context triple: [Oswald Jonas Memorial Collection, hasArchivalLevel, fonds]
-
A.
hasPreservationLevel
Indicates the degree or status of protection, conservation, or safeguarding applied to an entity.
-
B.
archivesLevel
chosen
Indicates that one entity is stored, classified, or maintained at a particular archival level or tier within an archival system.
-
C.
hasArchaeologicalLevel
Indicates that an entity is associated with a specific archaeological stratigraphic level or layer.
-
D.
isArchivalReleaseOf
Indicates that one entity is a later archival issue or re-release of another, typically preserving or restoring original material for historical or record-keeping purposes.
-
E.
hasArchiveArea
Indicates that an entity includes or is associated with a designated area used for archiving or long-term storage of materials.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 29, 2026, 8:46 p.m.