Triple
T13930290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Orme Copper Mines |
E334970
|
entity |
| Predicate | usedMiningTechnique |
P10926
|
FINISHED |
| Object | fire-setting |
—
|
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: fire-setting | Statement: [Great Orme Copper Mines, usedMiningTechnique, fire-setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMiningTechnique Context triple: [Great Orme Copper Mines, usedMiningTechnique, fire-setting]
-
A.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
C.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
D.
mainMiningMethod
chosen
Indicates the primary mining technique or process predominantly used in extracting resources at a given site or operation.
-
E.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa900a0819095eeb1bc46b0336e |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.