Triple
T9948694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rare Books and Special Collections Library |
E195270
|
entity |
| Predicate | isResearchFocused |
P43753
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rare Books and Special Collections Library, isResearchFocused, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResearchFocused Context triple: [Rare Books and Special Collections Library, isResearchFocused, true]
-
A.
hasResearchOrientation
chosen
Indicates that an entity is associated with a particular focus, direction, or approach in its research activities.
-
B.
isResearchInstitution
Indicates that an entity functions primarily as an organization dedicated to conducting scientific or scholarly research.
-
C.
isResearchHub
Indicates that an entity serves as a central location or focal point for conducting, coordinating, or supporting research activities.
-
D.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
E.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb659307c81908279adb641ceef86 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.