Triple
T2526476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalsa |
E56044
|
entity |
| Predicate | weaponryPrinciple |
P22495
|
FINISHED |
| Object | bearing arms for defense of justice |
—
|
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: bearing arms for defense of justice | Statement: [Khalsa, weaponryPrinciple, bearing arms for defense of justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponryPrinciple Context triple: [Khalsa, weaponryPrinciple, bearing arms for defense of justice]
-
A.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
D.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
E.
weaponDiscipline
chosen
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
- 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.