Triple
T34111763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amrit Vela |
E874855
|
entity |
| Predicate | valueInSikhism |
P178241
|
FINISHED |
| Object | highly meritorious |
—
|
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: highly meritorious | Statement: [Amrit Vela, valueInSikhism, highly meritorious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueInSikhism Context triple: [Amrit Vela, valueInSikhism, highly meritorious]
-
A.
roleInSikhTradition
Indicates the specific function, status, or position an entity holds within Sikh religious, cultural, or historical practices and institutions.
-
B.
numberOfTakhtsInSikhism
Indicates the relationship that specifies how many Takhts (seats of authority) there are within Sikhism.
-
C.
inJainism
Indicates that the subject is associated with, belongs to, or is characterized within the religious-philosophical tradition of Jainism.
-
D.
scriptForSikhReligiousTexts
Indicates the script or writing system used to write Sikh religious texts.
-
E.
strengthSikhSide
Indicates the relative level of power, capability, or military strength possessed by the Sikh side in a given context or interaction.
- F. None of above. chosen
Provenance (4 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb544848190aaeb8f766a95aaff |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.