Triple
T11451146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota Super Thermal Power Station |
E271396
|
entity |
| Predicate | usesBoilerType |
P47501
|
FINISHED |
| Object | coal-fired boiler |
—
|
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-fired boiler | Statement: [Kota Super Thermal Power Station, usesBoilerType, coal-fired boiler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBoilerType Context triple: [Kota Super Thermal Power Station, usesBoilerType, coal-fired boiler]
-
A.
boilerType
chosen
Indicates the specific kind or category of boiler associated with an entity, such as its design, fuel source, or operating characteristics.
-
B.
hasBoilerPosition
Indicates the spatial placement or designated location of a boiler relative to another object or within a given environment.
-
C.
hasBoilerPressure
Indicates that an entity possesses or is associated with a specific boiler pressure value.
-
D.
boilers
Indicates that an entity functions as or is equipped with boilers, typically for heating or generating steam.
-
E.
furnaceType
Indicates the specific kind or category of furnace associated with an entity.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.