Triple
T36186552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnamagnæan Manuscript Collection |
E1046861
|
entity |
| Predicate | digitizationStatus |
P185051
|
FINISHED |
| Object | partially digitized |
—
|
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: partially digitized | Statement: [Arnamagnæan Manuscript Collection, digitizationStatus, partially digitized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitizationStatus Context triple: [Arnamagnæan Manuscript Collection, digitizationStatus, partially digitized]
-
A.
digitizedBy
Indicates that a physical or analog item has been converted into digital form by a particular agent or organization.
-
B.
digitizationProjectFocus
Indicates that a digitization project is specifically directed toward or centered on a particular subject, collection, or type of material.
-
C.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
-
D.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
E.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.