Triple
T26536602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaigai River basin |
E671266
|
entity |
| Predicate | sourceRegionOfRunoff |
P116720
|
FINISHED |
| Object | Cardamom Hills |
—
|
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: Cardamom Hills | Statement: [Vaigai River basin, sourceRegionOfRunoff, Cardamom Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceRegionOfRunoff Context triple: [Vaigai River basin, sourceRegionOfRunoff, Cardamom Hills]
-
A.
waterSourceRegion
Indicates that a specified region serves as the geographic source or origin area of a particular body or supply of water.
-
B.
primaryRunoffSource
chosen
Indicates that one entity is the main origin or contributor of runoff (e.g., water, pollutants, or surface flow) affecting another entity.
-
C.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
-
D.
sourceBasin
Indicates that one entity is the drainage basin or watershed from which another entity (such as a river segment or water body) originates or receives its source waters.
-
E.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613fc19d08190a90a8dcac0b8e8d5 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:39 a.m.