Triple
T35761967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barite Hill gold deposit |
E1033598
|
entity |
| Predicate | hostLithology |
P17895
|
FINISHED |
| Object | felsic 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: felsic volcanic rocks | Statement: [Barite Hill gold deposit, hostLithology, felsic volcanic rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostLithology Context triple: [Barite Hill gold deposit, hostLithology, felsic volcanic rocks]
-
A.
lithologyAbove
Indicates that one rock or sediment layer directly overlies another in a vertical stratigraphic sequence.
-
B.
lithologyBelow
Indicates that one lithologic unit or rock layer is positioned stratigraphically beneath another.
-
C.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
D.
lithologyAffected
Indicates that one lithology is influenced, altered, or impacted in some way by another geological process, material, or condition.
-
E.
lithologyInFootwall
Indicates that a specified lithology occurs within the footwall block relative to a fault or structural discontinuity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c562848190ba1fe4f9cb7efa87 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.