Triple
T34188387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koderma district |
E877025
|
entity |
| Predicate | majorMineralResource |
P28979
|
FINISHED |
| Object | mica |
—
|
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: mica | Statement: [Koderma district, majorMineralResource, mica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorMineralResource Context triple: [Koderma district, majorMineralResource, mica]
-
A.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
-
B.
hasImportantMineral
chosen
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
C.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
D.
isAssociatedWithMineral
Indicates that there is a relationship or connection between an entity and a specific mineral, such as composition, presence, or relevance.
-
E.
economicGeology
Indicates a relationship where geological features, materials, or processes are studied or evaluated in terms of their economic value, such as for resource exploration, extraction, or utilization.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 1:55 a.m.