Triple
T5484817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle Mountain mining district |
E123552
|
entity |
| Predicate | hasHostRock |
P53497
|
FINISHED |
| Object | volcanic rocks |
—
|
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: volcanic rocks | Statement: [Battle Mountain mining district, hasHostRock, volcanic rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostRock Context triple: [Battle Mountain mining district, hasHostRock, volcanic rocks]
-
A.
hostRock
chosen
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
B.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
C.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.