Triple
T1742042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Gold Belt |
E38253
|
entity |
| Predicate | mineralizationType |
P31790
|
FINISHED |
| Object | vein gold deposits |
—
|
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: vein gold deposits | Statement: [Georgia Gold Belt, mineralizationType, vein gold deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralizationType Context triple: [Georgia Gold Belt, mineralizationType, vein gold deposits]
-
A.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
B.
mantleType
Indicates the type or classification of a mantle associated with an entity, specifying what kind of mantle it has.
-
C.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
D.
saltMineType
Indicates the specific kind or classification of a salt mine associated with an entity.
-
E.
metabolismType
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab3c2479148190badc616f8e2686d4 |
completed | March 6, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.