Triple
T1221421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reguliersgracht |
E26229
|
entity |
| Predicate | hasPeriodOfDevelopment |
P24285
|
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: [Reguliersgracht, hasPeriodOfDevelopment, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodOfDevelopment Context triple: [Reguliersgracht, hasPeriodOfDevelopment, 17th century]
-
A.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
hadGrowthPeriod
chosen
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
D.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
E.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be206c108190bb8a5d44fc516c98 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.