Triple
T18817343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugsworth Basin |
E460170
|
entity |
| Predicate | peakPeriodOfUse |
P4017
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Bugsworth Basin, peakPeriodOfUse, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPeriodOfUse Context triple: [Bugsworth Basin, peakPeriodOfUse, 19th century]
-
A.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
B.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
C.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
D.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
E.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b620248190afa21a6ce61e2cff |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.