Triple
T4538574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Plutonic Complex |
E107469
|
entity |
| Predicate | economicGeology |
P57932
|
FINISHED |
| Object | associated with mineral 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: associated with mineral deposits | Statement: [Coast Plutonic Complex, economicGeology, associated with mineral deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicGeology Context triple: [Coast Plutonic Complex, economicGeology, associated with mineral deposits]
-
A.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
B.
mineralogy
Indicates the study or characterization of the mineral composition and properties associated with an entity.
-
C.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
D.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
E.
naturalResources
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b8c4788190b35d110553013ff1 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:04 p.m.