Triple
T27070169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahobilam Narasimha temples |
E685300
|
entity |
| Predicate | hasSacredRiverNearby |
P143120
|
FINISHED |
| Object | Bhavanasi river |
—
|
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: Bhavanasi river | Statement: [Ahobilam Narasimha temples, hasSacredRiverNearby, Bhavanasi river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredRiverNearby Context triple: [Ahobilam Narasimha temples, hasSacredRiverNearby, Bhavanasi river]
-
A.
sacredRiverNearby
chosen
Indicates that there is a sacred river located in close proximity to the referenced entity.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
sacredRiver
Indicates that a river is regarded as holy or spiritually significant within a religious or cultural tradition.
-
D.
hasMythicalRiverConfluence
Indicates a relationship where a mythical or legendary river is believed to merge or join with another river or body of water.
-
E.
hasAncestralRiver
Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:27 a.m.