Triple
T38348629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdalene College Pepys Library |
E1041614
|
entity |
| Predicate | collectionEra |
P177585
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Magdalene College Pepys Library, collectionEra, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionEra Context triple: [Magdalene College Pepys Library, collectionEra, 17th century]
-
A.
eraOfCollection
chosen
Indicates the historical time period during which the collection was assembled or gathered.
-
B.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
C.
discoveryEra
Indicates the historical period or era during which the entity was discovered or first identified.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:30 p.m.