Triple
T7400280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rourkela industrial region |
E170728
|
entity |
| Predicate | coreIndustry |
P53279
|
FINISHED |
| Object | steel industry |
—
|
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: steel industry | Statement: [Rourkela industrial region, coreIndustry, steel industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreIndustry Context triple: [Rourkela industrial region, coreIndustry, steel industry]
-
A.
operatorIndustry
Indicates that an operator (such as a company or organization) is engaged in or associated with a particular industry sector.
-
B.
industryContext
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
C.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
D.
containsIndustry
chosen
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
E.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24dbf288190b8dfea455148841b |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.