Triple
T3614180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikh people |
E76559
|
entity |
| Predicate | coreArticleOfFaith |
P2154
|
FINISHED |
| Object | Kangha |
E276057
|
NE 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: Kangha | Statement: [Sikh people, coreArticleOfFaith, Kangha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kangha Context triple: [Sikh people, coreArticleOfFaith, Kangha]
-
A.
Kangha
chosen
Kangha is a small wooden comb that serves as one of the Five Ks in Sikhism, symbolizing cleanliness and discipline for initiated Sikhs.
-
B.
Kangar
Kangar is the main administrative and commercial center of the Malaysian state of Perlis.
-
C.
Kashin
Kashin is a historic town in western Russia known for its medieval heritage and location along the Kashinka River.
-
D.
Kangthir
Kangthir is the traditional council or governing body of the Karbi people, responsible for overseeing customary laws and community affairs.
-
E.
Shina
Shina is an Indo-Aryan language spoken primarily in the Gilgit-Baltistan region of Pakistan and surrounding Himalayan areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69b43316224081909372f1007becc663 |
completed | March 13, 2026, 3:53 p.m. |
Created at: March 8, 2026, 3:23 p.m.