Triple
T33224242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellampalli |
E850509
|
entity |
| Predicate | hasCoalCompany |
P92829
|
FINISHED |
| Object | Singareni Collieries Company Limited operations |
—
|
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: Singareni Collieries Company Limited operations | Statement: [Bellampalli, hasCoalCompany, Singareni Collieries Company Limited operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoalCompany Context triple: [Bellampalli, hasCoalCompany, Singareni Collieries Company Limited operations]
-
A.
hasCoalMiningCompany
chosen
Indicates that an entity is associated with or owns a company whose primary business is coal mining.
-
B.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
-
C.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
D.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
E.
coalMinedFrom
Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.