Triple
T11451155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota Super Thermal Power Station |
E271396
|
entity |
| Predicate | hasAshPond |
P99643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kota Super Thermal Power Station, hasAshPond, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAshPond Context triple: [Kota Super Thermal Power Station, hasAshPond, yes]
-
A.
containsFishpond
Indicates that one entity includes or has within its boundaries a fishpond.
-
B.
hasNearbyLake
Indicates that one entity is located close to or in the vicinity of a lake.
-
C.
hasLagoon
Indicates that one entity possesses, contains, or is characterized by a lagoon in relation to another entity or location.
-
D.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
E.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.