Triple
T34111801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitnem |
E874856
|
entity |
| Predicate | normativeCode |
P12028
|
FINISHED |
| Object | Sikh Rehat Maryada |
—
|
NE NERFINISHED |
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: Sikh Rehat Maryada | Statement: [Nitnem, normativeCode, Sikh Rehat Maryada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativeCode Context triple: [Nitnem, normativeCode, Sikh Rehat Maryada]
-
A.
normativeFor
chosen
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
hasNormativeCategory
Indicates that something is associated with a particular normative category, such as a standard, rule, or evaluative classification that prescribes how it ought to be regarded or treated.
-
D.
normativelyIncludes
Indicates that one norm or rule encompasses, subsumes, or otherwise includes another within its prescribed scope or requirements.
-
E.
standardCodeSystem
Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
- 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_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. |
Created at: May 1, 2026, 1:53 a.m.