Triple
T3614205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikh people |
E76559
|
entity |
| Predicate | martialTradition |
P18145
|
FINISHED |
| Object | Gatka |
—
|
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: Gatka | Statement: [Sikh people, martialTradition, Gatka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: martialTradition Context triple: [Sikh people, martialTradition, Gatka]
-
A.
martialArt
chosen
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
B.
isGrapplingArt
Indicates that the subject is a martial art or combat style primarily focused on grappling techniques such as holds, locks, and throws.
-
C.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
D.
traditionOrMovement
Indicates that one entity is a tradition, school, or movement associated with, derived from, or belonging to another entity.
-
E.
variantTraditions
Indicates that there exist differing or alternative traditions or customary practices associated with the same subject or context.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc279f6948190b9655a4cf3e77d89 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.