Triple
T8275824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Area of Willemstad, Inner City and Harbour |
E193543
|
entity |
| Predicate | dateOfConstructionPeriod |
P22153
|
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: [Historic Area of Willemstad, Inner City and Harbour, dateOfConstructionPeriod, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfConstructionPeriod Context triple: [Historic Area of Willemstad, Inner City and Harbour, dateOfConstructionPeriod, 17th century]
-
A.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
B.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
C.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
D.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
E.
constructionTime
Indicates the duration or specific point in time required to construct or build an 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798d69508190b581ad8a38730175 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.