Triple
T27198241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coimbatore district |
E683661
|
entity |
| Predicate | majorProtectedAreaNearby |
P67111
|
FINISHED |
| Object | Silent Valley National Park |
—
|
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: Silent Valley National Park | Statement: [Coimbatore district, majorProtectedAreaNearby, Silent Valley National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorProtectedAreaNearby Context triple: [Coimbatore district, majorProtectedAreaNearby, Silent Valley National Park]
-
A.
nearestMajorProtectedArea
Indicates the closest significant legally protected natural area to a given location or entity.
-
B.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
C.
isInlandWaterProtectedAreaNearby
Indicates that there is a protected inland water area located in close proximity to the referenced entity.
-
D.
nearbyProtectedSite
chosen
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
E.
hasNearbyProtectedAreaManagingOrganization
Indicates that an entity has a managing organization responsible for a protected area located nearby.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 9:35 a.m.