Triple
T15606940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joanina Library |
E375181
|
entity |
| Predicate | notableCollectionPeriod |
P116486
|
FINISHED |
| Object | 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: 16th century | Statement: [Joanina Library, notableCollectionPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCollectionPeriod Context triple: [Joanina Library, notableCollectionPeriod, 16th century]
-
A.
significantCollectionPeriod
Indicates that the time span over which something is gathered, measured, or accumulated is long or substantial enough to be considered important or impactful.
-
B.
typicalCollectionPeriodStart
Indicates the date or point in time when a standard or customary collection period begins.
-
C.
notablePeriodOfAward
Indicates the specific time span or period during which an award is considered notable or was actively held or recognized.
-
D.
notableCollectionIncludes
Indicates that a notable or significant collection contains or features the specified item as one of its components.
-
E.
hasNotabilityPeriod
chosen
Indicates the time span during which an entity is or was notable or prominent.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.