Triple
T9195734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagirathi River |
E220701
|
entity |
| Predicate | mouthFormation |
P86942
|
FINISHED |
| Object | forms Ganges at Devprayag with Alaknanda |
—
|
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: forms Ganges at Devprayag with Alaknanda | Statement: [Bhagirathi River, mouthFormation, forms Ganges at Devprayag with Alaknanda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthFormation Context triple: [Bhagirathi River, mouthFormation, forms Ganges at Devprayag with Alaknanda]
-
A.
mouthDirection
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
-
B.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
C.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
D.
fromMouth
Indicates that something originates from or is emitted out of a mouth.
-
E.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87c3a3c8190b60f19873ef6e1f8 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6745c17881908df72443e0800068 |
completed | April 1, 2026, 12:31 a.m. |
Created at: March 30, 2026, 7:25 p.m.