Triple
T25525347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aravalli region of Gujarat |
E639758
|
entity |
| Predicate | hasWaterSources |
P64067
|
FINISHED |
| Object | seasonal streams |
—
|
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: seasonal streams | Statement: [Aravalli region of Gujarat, hasWaterSources, seasonal streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterSources Context triple: [Aravalli region of Gujarat, hasWaterSources, seasonal streams]
-
A.
hasWaterResourceType
Indicates that an entity is associated with a specific type or category of water resource.
-
B.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
C.
hasWaterFeatures
chosen
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 3:09 p.m.