Triple
T15575745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Lima |
E374364
|
entity |
| Predicate | primaryMiningResource |
P64309
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Nova Lima, primaryMiningResource, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMiningResource Context triple: [Nova Lima, primaryMiningResource, gold]
-
A.
naturalResources
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
B.
primaryExtraction
Indicates that an entity is the main or initial source from which another entity, resource, or substance is obtained or derived.
-
C.
primaryOreTypes
chosen
Indicates the main types of ore that are predominantly associated with or extracted from a given entity.
-
D.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
E.
usesNaturalResource
Indicates that an entity makes use of a natural resource (such as water, minerals, or forests) to support its activities, processes, or functions.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2140388190a8df7b835eaa72ce |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.