Triple
T5430030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redruth |
E121461
|
entity |
| Predicate | historicalActivityPeak |
P4936
|
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: [Redruth, historicalActivityPeak, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalActivityPeak Context triple: [Redruth, historicalActivityPeak, 18th century]
-
A.
historicalPeak
chosen
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
D.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
E.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.