Triple
T352813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotch Library |
E7478
|
entity |
| Predicate | primaryLibraryFor |
P3294
|
FINISHED |
| Object | architecture |
—
|
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: architecture | Statement: [Rotch Library, primaryLibraryFor, architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLibraryFor Context triple: [Rotch Library, primaryLibraryFor, architecture]
-
A.
primaryResearchLibraryFor
Indicates that one entity serves as the main or principal research library resource for another entity.
-
B.
isMainLibraryOf
chosen
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
C.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
D.
library
Indicates that an entity functions as or is associated with a library, typically as a place or system for storing, organizing, and providing access to collections of information resources.
-
E.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7f1be88190964ddcbb6a05f021 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.