Triple
T26412236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundargarh district |
E663990
|
entity |
| Predicate | hasMajorMiningCenter |
P105974
|
FINISHED |
| Object | Rourkela |
—
|
NE NERFINISHED |
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: Rourkela | Statement: [Sundargarh district, hasMajorMiningCenter, Rourkela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorMiningCenter Context triple: [Sundargarh district, hasMajorMiningCenter, Rourkela]
-
A.
hasMajorCommercialCentre
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
B.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
C.
hasMiningInfrastructure
Indicates that an entity possesses or is equipped with facilities, equipment, or systems used for mining activities.
-
D.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
E.
containsMiningTown
chosen
Indicates that a location or area includes within its boundaries a town whose primary activity or identity is based on mining.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 26, 2026, 11:38 p.m.