Triple
T29812139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Tavy |
E756994
|
entity |
| Predicate | historicalPeriodOfMiningPeak |
P117229
|
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: [Mary Tavy, historicalPeriodOfMiningPeak, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfMiningPeak Context triple: [Mary Tavy, historicalPeriodOfMiningPeak, 19th century]
-
A.
peakMiningPeriod
chosen
Indicates the time period during which mining activity for a given resource or location was at its highest level.
-
B.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
C.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
D.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
E.
miningHistory
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: April 29, 2026, 5:24 p.m.