Triple
T33195592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mullaperiyar Dam |
E849747
|
entity |
| Predicate | nearbyCityBenefiting |
P195944
|
FINISHED |
| Object | Madurai |
—
|
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: Madurai | Statement: [Mullaperiyar Dam, nearbyCityBenefiting, Madurai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCityBenefiting Context triple: [Mullaperiyar Dam, nearbyCityBenefiting, Madurai]
-
A.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
-
B.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
C.
downstreamCityBenefited
Indicates that one city gains advantages or positive impacts as a result of actions, conditions, or resources originating from another city located upstream.
-
D.
nearbyCityServed
Indicates that a city is geographically close enough to another city to be considered within its service or support area.
-
E.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 1, 2026, 1:29 a.m.