Triple
T4172369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swaraj |
E86391
|
entity |
| Predicate | normativelyValues |
P33441
|
FINISHED |
| Object | non-violence in political struggle |
—
|
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: non-violence in political struggle | Statement: [Swaraj, normativelyValues, non-violence in political struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativelyValues Context triple: [Swaraj, normativelyValues, non-violence in political struggle]
-
A.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
-
C.
normativeGoal
chosen
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
D.
normTakesValuesIn
Indicates that a norm or standard is defined such that its possible outcomes or assigned values lie within a specified set or range.
-
E.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02e65b548190be095df62091b960 |
completed | March 9, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.