Triple
T27523029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictorial Collections |
E694760
|
entity |
| Predicate | repositoryFor |
P162475
|
FINISHED |
| Object | archival pictorial materials |
—
|
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: archival pictorial materials | Statement: [Pictorial Collections, repositoryFor, archival pictorial materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryFor Context triple: [Pictorial Collections, repositoryFor, archival pictorial materials]
-
A.
hasRepository
Indicates that an entity maintains or is associated with a specific repository (such as a code, data, or content store).
-
B.
registryFor
Indicates a relationship where one entity serves as an official registry or record-keeping authority for another entity or set of items.
-
C.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
D.
officialRepositoryFor
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
-
E.
usesRepository
Indicates that one entity relies on, accesses, or interacts with a particular repository as a resource or data source.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2d7040819094509bbe723ce9db |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:22 p.m.