Triple
T13936580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotton Library |
E335135
|
entity |
| Predicate | collectionFormationPeriod |
P52657
|
FINISHED |
| Object | late 16th 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: late 16th century | Statement: [Cotton Library, collectionFormationPeriod, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionFormationPeriod Context triple: [Cotton Library, collectionFormationPeriod, late 16th century]
-
A.
mainFormationPeriod
chosen
Indicates the time span during which something was primarily formed or took shape.
-
B.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
C.
departmentFormed
Indicates that a specific department has been created or established, often at a particular time or under certain conditions.
-
D.
hasFormulationPeriod
Indicates the time span during which something is planned, designed, or developed before it is finalized or implemented.
-
E.
organisedSince
Indicates that an entity has been formally organized or established starting from a specified point in time.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.