Triple
T34914713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwin estuary (historically) |
E1006968
|
entity |
| Predicate | approximateSiltationPeriod |
P199449
|
FINISHED |
| Object | late Middle Ages |
—
|
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: late Middle Ages | Statement: [Zwin estuary (historically), approximateSiltationPeriod, late Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSiltationPeriod Context triple: [Zwin estuary (historically), approximateSiltationPeriod, late Middle Ages]
-
A.
erosionRate
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
B.
erosionTimescale
Indicates the characteristic duration over which erosion significantly alters or removes a material, surface, or feature.
-
C.
erosionProcessDuration
Indicates the length of time over which an erosion process occurs or is observed.
-
D.
reservoirAge
Indicates the length of time that a reservoir has existed or been in use.
-
E.
historicalWaterwaySiltedUpBy
Indicates that a formerly navigable or flowing waterway has become filled or obstructed by silt due to the action or influence of the related entity.
- F. None of above. chosen
Provenance (4 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69ff397d6a2081908fa8f62e8902421b |
completed | May 9, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4 p.m.