Triple
T27395010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahanandi |
E691653
|
entity |
| Predicate | hasSacredWaterBelief |
P160284
|
FINISHED |
| Object | temple tank waters considered holy |
—
|
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: temple tank waters considered holy | Statement: [Mahanandi, hasSacredWaterBelief, temple tank waters considered holy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredWaterBelief Context triple: [Mahanandi, hasSacredWaterBelief, temple tank waters considered holy]
-
A.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
B.
hasMythologicalBelief
Indicates that an entity holds or subscribes to a particular mythological belief or set of mythological beliefs.
-
C.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
D.
hasSacredNarrative
Indicates that one entity possesses, contains, or is associated with a sacred or religiously significant narrative related to another entity.
-
E.
sacredWaterBody
chosen
Indicates that a water body holds religious or spiritual significance within a belief system or ritual practice.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 12:27 p.m.