Triple
T29337954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhalaut Sub-Branch |
E743960
|
entity |
| Predicate | sourceCanal |
P109759
|
FINISHED |
| Object | Western Yamuna Canal |
E202668
|
NE 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: Western Yamuna Canal | Statement: [Bhalaut Sub-Branch, sourceCanal, Western Yamuna Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCanal Context triple: [Bhalaut Sub-Branch, sourceCanal, Western Yamuna Canal]
-
A.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
B.
usedCanal
Indicates that an entity made use of a canal as a route, resource, or means to perform an action or achieve a purpose.
-
C.
originalCanal
chosen
Indicates that one canal is the initial or source canal from which another canal originates or is derived.
-
D.
feedsCanal
Indicates that one water source supplies or channels water into a canal.
-
E.
canalProject
Indicates that an entity is involved in, associated with, or designated as a canal construction or development project.
- F. None of above.
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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a262d48ed7c8190a11a4c7bd47a34c4 |
completed | June 8, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 1:32 p.m.