Triple
T2676176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumbarton Oaks |
E56463
|
entity |
| Predicate | libraryFocus |
P30099
|
FINISHED |
| Object | Byzantine studies |
—
|
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: Byzantine studies | Statement: [Dumbarton Oaks, libraryFocus, Byzantine studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: libraryFocus Context triple: [Dumbarton Oaks, libraryFocus, Byzantine studies]
-
A.
libraryCollectionFocus
chosen
Indicates that a library’s collection is primarily oriented toward or specialized in a particular subject, audience, or type of material.
-
B.
libraryCatalog
Indicates a relationship where a library’s catalog system organizes, indexes, and provides access information for the items held in the library’s collection.
-
C.
book2Focus
Indicates that attention, interest, or emphasis is directed toward a particular book.
-
D.
bookCategory
Indicates the classification or genre category to which a given book belongs.
-
E.
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.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.