Triple
T34130366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhanbad railway division |
E875406
|
entity |
| Predicate | hasMainIndustryLink |
P13077
|
FINISHED |
| Object | coal 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: coal mining | Statement: [Dhanbad railway division, hasMainIndustryLink, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainIndustryLink Context triple: [Dhanbad railway division, hasMainIndustryLink, coal mining]
-
A.
hasPrincipalIndustry
chosen
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
B.
hasIndustryTies
Indicates that an entity maintains professional, financial, or organizational connections with a particular industry or sector.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
hasEconomicLinkType
Indicates the type or nature of the economic relationship or linkage that exists between two entities.
-
E.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a016cc5abcc8190b64094c777b40f6f |
completed | May 11, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a016b997ecc8190818207c57b9cbf17 |
completed | May 11, 2026, 5:39 a.m. |
Created at: May 1, 2026, 1:53 a.m.