Triple
T7392825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Round Mountain Gold Mine |
E170542
|
entity |
| Predicate | depositType |
P76327
|
FINISHED |
| Object | epithermal 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: epithermal gold deposit | Statement: [Round Mountain Gold Mine, depositType, epithermal gold deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositType Context triple: [Round Mountain Gold Mine, depositType, epithermal gold deposit]
-
A.
typeOfDeposits
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
-
B.
depositTypeRecognized
Indicates that the type of deposit involved in a transaction or context has been identified and classified as a valid, known category.
-
C.
typeOfDepositInsurance
Indicates the specific kind or category of deposit insurance that applies to a financial account or institution.
-
D.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
-
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. 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f224790c819099ceb7c7ac8d00f6 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:09 p.m.