Triple
T37285296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota region |
E925516
|
entity |
| Predicate | receivesPowerFrom |
P11313
|
FINISHED |
| Object | Kota Super Thermal Power Station |
—
|
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: Kota Super Thermal Power Station | Statement: [Kota region, receivesPowerFrom, Kota Super Thermal Power Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesPowerFrom Context triple: [Kota region, receivesPowerFrom, Kota Super Thermal Power Station]
-
A.
suppliesPowerTo
chosen
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
B.
derivesPowerFrom
Indicates that one entity obtains or is granted its power, authority, or energy as a result of another entity.
-
C.
hasPowerTerminal
Indicates that an entity is equipped with or connected to a power terminal through which electrical power can be supplied or distributed.
-
D.
suppliesPowerUnitsTo
Indicates that one entity provides electrical power units as a resource or input to another entity.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:16 p.m.