Triple
T29506128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadri |
E748516
|
entity |
| Predicate | energyInfrastructureHub |
P118200
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dadri, energyInfrastructureHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyInfrastructureHub Context triple: [Dadri, energyInfrastructureHub, true]
-
A.
energyInfrastructureRole
Indicates the functional role or purpose an entity has within an energy-related infrastructure system (e.g., generation, transmission, distribution, or storage).
-
B.
infrastructureAssociatedWith
Indicates a relationship where a piece of infrastructure is functionally or contextually connected to, supports, or is used by another entity.
-
C.
energyHub
chosen
Indicates a central entity that collects, manages, and distributes energy or power among connected entities or systems.
-
D.
relatedInfrastructure
Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
-
E.
plannedPowerplant
Indicates that a power plant is intended or scheduled to be built or developed, but is not yet constructed or operational.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 4:28 p.m.