Triple
T16799988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon Ore Mountain mining region |
E408328
|
entity |
| Predicate | timePeriodOfIntensiveMining |
P117229
|
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: [Saxon Ore Mountain mining region, timePeriodOfIntensiveMining, late Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfIntensiveMining Context triple: [Saxon Ore Mountain mining region, timePeriodOfIntensiveMining, late Middle Ages]
-
A.
peakMiningPeriod
chosen
Indicates the time period during which mining activity for a given resource or location was at its highest level.
-
B.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
C.
historicalPeriodOfIntensiveQuarrying
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
-
D.
miningStarted
Indicates that the process of extracting resources from a source or site has begun.
-
E.
iceCoreDrillingPeriod
Indicates the span of time during which an ice core drilling activity takes 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2acd3548190a5f6ce7d1cf74117 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.