Triple
T28842602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amber State |
E728359
|
entity |
| Predicate | rulingReligion |
P55284
|
FINISHED |
| Object | Hinduism (Kachwaha Rajputs) |
—
|
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: Hinduism (Kachwaha Rajputs) | Statement: [Amber State, rulingReligion, Hinduism (Kachwaha Rajputs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingReligion Context triple: [Amber State, rulingReligion, Hinduism (Kachwaha Rajputs)]
-
A.
dominantReligionPolicy
Indicates the policy or stance an authority adopts toward the religion that holds dominant or majority status within a given context.
-
B.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
C.
religionOfCourt
Indicates the religious affiliation associated with a particular court.
-
D.
hasPrimaryReligionOfRulers
chosen
Indicates that the specified religion is the main or official faith practiced or endorsed by the rulers of an entity.
-
E.
rulerReligion
Indicates that a ruler adheres to, practices, or is officially associated with a particular religion.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6597467a081908e0048ab758bd889 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:41 a.m.