Triple
T17855009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iultinsky District |
E445907
|
entity |
| Predicate | formerKeyIndustry |
P129420
|
FINISHED |
| Object | tin mining |
—
|
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: tin mining | Statement: [Iultinsky District, formerKeyIndustry, tin mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerKeyIndustry Context triple: [Iultinsky District, formerKeyIndustry, tin mining]
-
A.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
-
B.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
C.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
D.
operatorIndustry
Indicates that an operator (such as a company or organization) is engaged in or associated with a particular industry sector.
-
E.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978af9b0819091780281344f5352 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:17 a.m.