Triple
T7903141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinderdijk |
E183504
|
entity |
| Predicate | windmillsConstructionPeriod |
P22153
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Kinderdijk, windmillsConstructionPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windmillsConstructionPeriod Context triple: [Kinderdijk, windmillsConstructionPeriod, 18th century]
-
A.
windmillType
Indicates that one entity is classified as a specific type or category of windmill in relation to another entity.
-
B.
hasWindmill
Indicates that one entity possesses, contains, or features a windmill as part of it or on its premises.
-
C.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
D.
windmillFunction
Indicates that something serves as or performs the function of a windmill, typically converting wind energy into mechanical or electrical power.
-
E.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a41b0fc81909890f2e4f432a5cf |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.