Triple
T18975916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mata Sahib Kaur |
E464294
|
entity |
| Predicate | typeOfReverence |
P5315
|
FINISHED |
| Object | spiritual reverence |
—
|
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: spiritual reverence | Statement: [Mata Sahib Kaur, typeOfReverence, spiritual reverence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfReverence Context triple: [Mata Sahib Kaur, typeOfReverence, spiritual reverence]
-
A.
venerationType
chosen
Indicates the specific manner or category of reverence or worship directed toward an entity.
-
B.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
-
C.
basisOfVeneration
Indicates the reason, quality, or attribute for which something or someone is regarded with reverence or veneration.
-
D.
ritualAttitude
Indicates an entity’s characteristic stance, mindset, or emotional orientation toward a ritual or ritual practice.
-
E.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61f96c88190b9a25158e0b012ca |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon