Triple
T28033027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesa Falls Tuff eruption |
E708322
|
entity |
| Predicate | depositName |
P163648
|
FINISHED |
| Object | Mesa Falls Tuff |
—
|
NE NERFINISHED |
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: Mesa Falls Tuff | Statement: [Mesa Falls Tuff eruption, depositName, Mesa Falls Tuff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositName Context triple: [Mesa Falls Tuff eruption, depositName, Mesa Falls Tuff]
-
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.
oreDeposit
Indicates the presence or occurrence of a concentrated natural accumulation of ore at or within a specified location or geological context.
-
D.
depositProtectionPillarName
Indicates the specific named pillar or component under which deposit protection is organized or classified.
-
E.
oreDepositType
Indicates the specific classification of an ore deposit based on how it formed or its characteristic geological features.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63c7507dc81909db7f9b46f012c76 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:18 p.m.