Triple
T27523161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of the Book collections |
E694764
|
entity |
| Predicate | collectsFromPeriod |
P49868
|
FINISHED |
| Object | early modern period |
—
|
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: early modern period | Statement: [History of the Book collections, collectsFromPeriod, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsFromPeriod Context triple: [History of the Book collections, collectsFromPeriod, early modern period]
-
A.
hasCollectionFromPeriod
chosen
Indicates that a collection originates from, or is associated with, a specific historical or temporal period.
-
B.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
C.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
D.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
E.
commonInPeriod
Indicates that something frequently occurs, appears, or is prevalent during a specified time period.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 1:22 p.m.