Triple
T19381817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parashurama Kshetra |
E484828
|
entity |
| Predicate | hasDeityCult |
P85900
|
FINISHED |
| Object | Parashurama worship |
—
|
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: Parashurama worship | Statement: [Parashurama Kshetra, hasDeityCult, Parashurama worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeityCult Context triple: [Parashurama Kshetra, hasDeityCult, Parashurama worship]
-
A.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
B.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
C.
hasCultEpithetOfDeity
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
D.
worshippedDeityCulture
chosen
Indicates that a particular culture reveres, honors, or practices religious devotion toward a specific deity.
-
E.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a6075a88190aed7afa3b8fd3021 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.