Triple
T3060145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Corner Bookstore |
E60577
|
entity |
| Predicate | usedAsBookstoreFrom |
P40799
|
FINISHED |
| Object | 1828 |
—
|
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: 1828 | Statement: [Old Corner Bookstore, usedAsBookstoreFrom, 1828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBookstoreFrom Context triple: [Old Corner Bookstore, usedAsBookstoreFrom, 1828]
-
A.
operatedBookstore
Indicates that one entity managed and ran the day-to-day operations of a bookstore owned or controlled by another entity.
-
B.
usesBookAs
Indicates that one entity employs or treats a book as a particular tool, resource, or role in a given context.
-
C.
storeType
chosen
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
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.
purchasedFrom
Indicates that one entity bought or acquired something from another entity as the seller or source.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9cf9188190b43f50edc009030d |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.