Triple
T34276976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koynanagar |
E879484
|
entity |
| Predicate | powerInfrastructureNearby |
P120742
|
FINISHED |
| Object | Koyna Hydroelectric Project |
—
|
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: Koyna Hydroelectric Project | Statement: [Koynanagar, powerInfrastructureNearby, Koyna Hydroelectric Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerInfrastructureNearby Context triple: [Koynanagar, powerInfrastructureNearby, Koyna Hydroelectric Project]
-
A.
hasNearbyPowerPlants
chosen
Indicates that one entity is located close to one or more power plants.
-
B.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
C.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
-
D.
adjacentToInfrastructure
Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
-
E.
nearbyIndustrialInstallation
Indicates that one entity is located close to an industrial facility or installation.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:56 a.m.