Triple
T10982686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagger Library |
E259546
|
entity |
| Predicate | hasSpecialCollectionsDepartment |
P35799
|
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: [Jagger Library, hasSpecialCollectionsDepartment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialCollectionsDepartment Context triple: [Jagger Library, hasSpecialCollectionsDepartment, yes]
-
A.
hasSpecialCollections
chosen
Indicates that an entity possesses or maintains distinct, curated collections that are set apart from its general holdings.
-
B.
hasCuratorialDepartment
Indicates that an item or entity is associated with a specific curatorial department responsible for its care, management, or interpretation.
-
C.
hasCulturalDepartment
Indicates that an entity possesses or maintains a dedicated department responsible for cultural activities, programs, or affairs.
-
D.
hasMuseumOrTreasureHouse
Indicates that an entity contains, hosts, or is associated with a museum or treasure house.
-
E.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772eb518c8190a885a417815f2ff6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.