Triple
T38125249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maratha military leadership at Panipat |
E952049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical collective entity |
C1884
|
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: historical collective entity Context triple: [Maratha military leadership at Panipat, instanceOf, historical collective entity]
-
A.
collective political entity
A collective political entity is an organized group of individuals or communities that exercises or claims shared authority, representation, and decision-making power within a defined political framework.
-
B.
historical group
chosen
A historical group is a collection of people connected by a shared identity, purpose, or activity that existed and acted within a specific past time period.
-
C.
ancient political entity
An ancient political entity is a historically situated, organized community or state that exercised authority, governance, and control over a defined territory and population in antiquity.
-
D.
historical maritime entity
A historical maritime entity is an organization, vessel, or institution from the past that operated on or was fundamentally connected to the sea, shaping or reflecting the maritime activities, trade, warfare, or exploration of its era.
-
E.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.