Triple
T36183302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Collection |
E1046774
|
entity |
| Predicate | digitisedBy |
P22918
|
FINISHED |
| Object | Parker Library on the Web project |
—
|
NE NERFINISHED |
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: Parker Library on the Web project | Statement: [Parker Collection, digitisedBy, Parker Library on the Web project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitisedBy Context triple: [Parker Collection, digitisedBy, Parker Library on the Web project]
-
A.
digitizedBy
chosen
Indicates that a physical or analog item has been converted into digital form by a particular agent or organization.
-
B.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
C.
digitalLibraryName
Indicates the name assigned to a digital library in which a resource or collection is managed or accessed.
-
D.
cataloguedWith
Indicates that an item has been recorded, classified, or registered using a particular cataloging system, method, or identifier.
-
E.
digitizationProjectFocus
Indicates that a digitization project is specifically directed toward or centered on a particular subject, collection, or type of material.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.