Triple
T25331469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandel Thermal Power Station |
E635162
|
entity |
| Predicate | ashByproduct |
P65738
|
FINISHED |
| Object | bottom ash |
—
|
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: bottom ash | Statement: [Bandel Thermal Power Station, ashByproduct, bottom ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ashByproduct Context triple: [Bandel Thermal Power Station, ashByproduct, bottom ash]
-
A.
ashDisposal
Indicates the method or process by which ash is removed, handled, or disposed of from a source or system.
-
B.
secondaryProducts
chosen
Indicates that certain entities arise as secondary or byproduct outputs from a primary process, activity, or production.
-
C.
notableSubstanceReleased
Indicates that an entity has released or emitted a particular notable substance.
-
D.
decayProduct
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
E.
usesAshesFrom
Indicates that one entity makes use of ashes originating from another entity as a resource, material, or component in some process or context.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c5f86c81908cf1ce29669bafbe |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:30 p.m.