Triple
T6631045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coniston Fells |
E149923
|
entity |
| Predicate | hasMiningHistory |
P29776
|
FINISHED |
| Object | copper mining |
—
|
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: copper mining | Statement: [Coniston Fells, hasMiningHistory, copper mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningHistory Context triple: [Coniston Fells, hasMiningHistory, copper mining]
-
A.
miningHistory
chosen
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
B.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
C.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
D.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
E.
hasSettlementHistory
Indicates that an entity has a documented history of human settlement or habitation in relation to another entity (such as a place or time period).
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.