Triple
T15769063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gove bauxite mine |
E382300
|
entity |
| Predicate | hasMiningLease |
P120263
|
FINISHED |
| Object | Gove Peninsula mining leases |
—
|
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: Gove Peninsula mining leases | Statement: [Gove bauxite mine, hasMiningLease, Gove Peninsula mining leases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningLease Context triple: [Gove bauxite mine, hasMiningLease, Gove Peninsula mining leases]
-
A.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
-
B.
hasMiningLicenseJurisdiction
Indicates that an authority or region has legal jurisdiction over the issuance, regulation, or enforcement of a mining license.
-
C.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
D.
hasMiningProject
Indicates that an entity is associated with, operates, or is responsible for a mining project.
-
E.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
- F. None of above. chosen
Provenance (4 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051951bac8190a7d45f3612c6de72 |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.