Triple
T18054676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Field lignite mine |
E432005
|
entity |
| Predicate | extractionType |
P92403
|
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: [South Field lignite mine, extractionType, surface mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extractionType Context triple: [South Field lignite mine, extractionType, surface mining]
-
A.
hasExtractionType
chosen
Indicates that one entity is associated with a specific method, category, or mode by which something is extracted from it or through it.
-
B.
extractedIn
Indicates that one entity is obtained, derived, or separated from another entity through an extraction process.
-
C.
overseesExtractionOf
Indicates that one entity supervises, manages, or has responsibility for the process by which another entity is extracted or obtained.
-
D.
canExtract
Indicates that one entity has the ability or permission to extract or derive something from another entity or source.
-
E.
extractedBy
Indicates that one entity is obtained, derived, or separated from another entity through some extraction process or method.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c101dfb081908dc66f4b4967d8c7 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.