Triple
T32352476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Home Guards |
E826642
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil defence auxiliary |
C31567
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: civil defence auxiliary Context triple: [Tamil Nadu Home Guards, instanceOf, civil defence auxiliary]
-
A.
civil defence equipment
Civil defence equipment comprises tools, devices, and systems designed to protect civilians, support emergency response, and mitigate the impacts of disasters, conflicts, or other large-scale threats.
-
B.
civilian auxiliary organization
chosen
A civilian auxiliary organization is a volunteer-based group of non-military citizens that supports and augments the capabilities, missions, or services of a governmental or official institution, often in areas like emergency response, public safety, or community outreach.
-
C.
civil emergency service
A civil emergency service is a public organization responsible for preparing for, responding to, and managing non-military crises and disasters to protect people, property, and the environment.
-
D.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
E.
auxiliary military personnel
Auxiliary military personnel are non-regular service members who provide specialized or supporting functions—such as logistics, medical aid, intelligence, or technical services—to enhance and sustain the operations of a primary armed force.
- F. None of above.
Provenance (1 batch)
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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:49 a.m.