Triple
T34816149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magha Mela |
E1003641
|
entity |
| Predicate | heldOnRiver |
P180780
|
FINISHED |
| Object | Ganges |
—
|
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: Ganges | Statement: [Magha Mela, heldOnRiver, Ganges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOnRiver Context triple: [Magha Mela, heldOnRiver, Ganges]
-
A.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
B.
plannedOnRiver
Indicates that something is intended or designed to be located, constructed, or carried out on or along a river.
-
C.
linkedToRiver
chosen
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
builtOnRiver
Indicates that a structure or settlement is constructed directly alongside or spanning a particular river.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab971548190a1e0a1e5ffd5b85d |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.