Triple
T20207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tozzer Library |
E401
|
entity |
| Predicate | primaryResearchLibraryFor |
P1842
|
FINISHED |
| Object | anthropology |
—
|
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: anthropology | Statement: [Tozzer Library, primaryResearchLibraryFor, anthropology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResearchLibraryFor Context triple: [Tozzer Library, primaryResearchLibraryFor, anthropology]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
peerReviewed
Indicates that a work, study, or submission has been evaluated and critiqued by qualified experts in the same field before acceptance or publication.
-
C.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
D.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
E.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a24703cb988190ad2bc181d27829e4 |
completed | Feb. 28, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_69a24650f1f0819081e638fafd18d687 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a24702d4988190a54a4e578b7c919e |
completed | Feb. 28, 2026, 1:38 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.