Triple
T35794933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharana Kumbha |
E1034806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian military leader |
C22817
|
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: Indian military leader Context triple: [Maharana Kumbha, instanceOf, Indian military leader]
-
A.
Military leader
chosen
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
B.
Chief of Army Staff of India
The Chief of Army Staff of India is the professional head and highest-ranking officer of the Indian Army, responsible for its command, operational readiness, and overall administration under the authority of the Government of India.
-
C.
Pakistani general
A Pakistani general is a high-ranking military officer in Pakistan's armed forces responsible for strategic planning, command of large military formations, and advising national leadership on defense and security matters.
-
D.
Indian Air Force officer
An Indian Air Force officer is a commissioned leader in India's aerial defense forces responsible for planning, directing, and executing air operations, managing personnel and resources, and upholding national security and military discipline.
-
E.
Vietnamese military leader
A Vietnamese military leader is a high-ranking commander responsible for planning, directing, and overseeing Vietnam’s armed forces in defense, strategic operations, and national security.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.