Triple
T16141198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alderley Edge escarpment |
E391657
|
entity |
| Predicate | hasMiningHistoryOf |
P29776
|
FINISHED |
| Object | copper |
—
|
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 | Statement: [Alderley Edge escarpment, hasMiningHistoryOf, copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningHistoryOf Context triple: [Alderley Edge escarpment, hasMiningHistoryOf, copper]
-
A.
miningHistory
chosen
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
B.
hasHistoricMine
Indicates that an entity possesses, contains, or is the site of a mine that is of historical significance.
-
C.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
D.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
E.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a087c848190aba9ed2ccb422427 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.