Triple
T14927365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conquest of Goa (1510) |
E372166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Indian history |
C34617
|
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: event in Indian history Context triple: [conquest of Goa (1510), instanceOf, event in Indian history]
-
A.
event in the Indian independence movement
An event in the Indian independence movement is a historically significant occurrence—such as a protest, law, campaign, negotiation, or act of resistance—that contributed to India’s struggle to end British colonial rule.
-
B.
Indian national event
An Indian national event is a significant occasion officially recognized and celebrated across India to commemorate historical milestones, cultural heritage, or national achievements.
-
C.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
-
D.
era in South Indian history
An era in South Indian history is a distinct time period characterized by specific dynasties, cultural developments, political structures, and socio-economic patterns that shaped the region’s historical trajectory.
-
E.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
- F. None of above. chosen
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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:35 a.m.