Triple
T20465028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laxey Mines |
E502024
|
entity |
| Predicate | endOfCommercialMining |
P17533
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Laxey Mines, endOfCommercialMining, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfCommercialMining Context triple: [Laxey Mines, endOfCommercialMining, early 20th century]
-
A.
miningActivityEnd
chosen
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
B.
endOfMainCommercialUseDecade
Indicates the decade in which the primary or main commercial use of something comes to an end.
-
C.
closedAsCommercialMine
Indicates that a mine ceased operations specifically as a commercial mining enterprise.
-
D.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
E.
miningStarted
Indicates that the process of extracting resources from a source or site has begun.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a9489081908990c691a36ba04d |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.