Triple
T34060609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vemulavada |
E873482
|
entity |
| Predicate | religiousPlurality |
P45
|
FINISHED |
| Object | primarily Hindu 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: primarily Hindu worship | Statement: [Vemulavada, religiousPlurality, primarily Hindu worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPlurality Context triple: [Vemulavada, religiousPlurality, primarily Hindu worship]
-
A.
religionDiversity
Indicates the degree to which multiple distinct religions are present and represented within a given context or group.
-
B.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
C.
isMultiReligious
Indicates that an entity is associated with or practices multiple religions rather than adhering to just one.
-
D.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
E.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:52 a.m.