Triple
T21495434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlin Trend mining district |
E530338
|
entity |
| Predicate | depositStyle |
P109495
|
FINISHED |
| Object | epigenetic sediment-hosted gold deposit |
—
|
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: epigenetic sediment-hosted gold deposit | Statement: [Carlin Trend mining district, depositStyle, epigenetic sediment-hosted gold deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositStyle Context triple: [Carlin Trend mining district, depositStyle, epigenetic sediment-hosted gold deposit]
-
A.
depositType
Indicates the specific kind or category of deposit associated with an account, transaction, or financial arrangement.
-
B.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
-
C.
depositProtectionPillarName
Indicates the specific named pillar or component under which deposit protection is organized or classified.
-
D.
oreDepositType
chosen
Indicates the specific classification of an ore deposit based on how it formed or its characteristic geological features.
-
E.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea575f2c81909cc0607c4b529f8d |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.