Triple
T22437768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred Guilder Print |
E554670
|
entity |
| Predicate | estimatedDateOfCreation |
P13262
|
FINISHED |
| Object | c. 1647–1649 |
—
|
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: c. 1647–1649 | Statement: [Hundred Guilder Print, estimatedDateOfCreation, c. 1647–1649]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDateOfCreation Context triple: [Hundred Guilder Print, estimatedDateOfCreation, c. 1647–1649]
-
A.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
B.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
-
C.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
D.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
E.
laterCreationDate
Indicates that one entity was created at a later date or time than the other entity.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15adf52f08190a5b592be3e68af0f |
completed | April 29, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.