Triple
T3357583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bou Craa |
E70641
|
entity |
| Predicate | hasMiningMethod |
P10923
|
FINISHED |
| Object | surface 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: surface mining | Statement: [Bou Craa, hasMiningMethod, surface mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningMethod Context triple: [Bou Craa, hasMiningMethod, surface mining]
-
A.
miningMethod
chosen
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
mainMiningMethod
Indicates the primary mining technique or process predominantly used in extracting resources at a given site or operation.
-
C.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
D.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
E.
hasProofMethod
Indicates that there exists a specific method or technique used to establish or demonstrate the validity of something (such as a statement, claim, or theorem).
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb244435c81908e35d2aa36ec4f46 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.