Triple
T2526512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amrit Sanchar |
E56045
|
entity |
| Predicate | requiresVows |
P23834
|
FINISHED |
| Object | commitment to Sikh Rehat Maryada |
—
|
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: commitment to Sikh Rehat Maryada | Statement: [Amrit Sanchar, requiresVows, commitment to Sikh Rehat Maryada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresVows Context triple: [Amrit Sanchar, requiresVows, commitment to Sikh Rehat Maryada]
-
A.
vowsLocation
Indicates the place where vows are made, exchanged, or formally declared between parties.
-
B.
hasVow
chosen
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
C.
requiresMOS
Indicates that one entity depends on or mandates a specific Military Occupational Specialty (MOS) qualification associated with another entity in order to be valid or applicable.
-
D.
primaryVows
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
E.
supportsAssertionLibraries
Indicates that one entity provides compatibility with or functionality for using specific assertion libraries in conjunction with 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.