Triple
T27458648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajgaivinath Temple, Sultanganj |
E692669
|
entity |
| Predicate | associatedRiverJourney |
P201387
|
FINISHED |
| Object | Sultanganj to Deoghar pilgrimage route |
—
|
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: Sultanganj to Deoghar pilgrimage route | Statement: [Ajgaivinath Temple, Sultanganj, associatedRiverJourney, Sultanganj to Deoghar pilgrimage route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRiverJourney Context triple: [Ajgaivinath Temple, Sultanganj, associatedRiverJourney, Sultanganj to Deoghar pilgrimage route]
-
A.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
B.
linkedToRiver
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
-
C.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
D.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fff09ce63881908e7f91a3d35d969f |
completed | May 10, 2026, 2:42 a.m. |
Created at: April 27, 2026, 12:49 p.m.