Triple
T37044107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sholinghur |
E916859
|
entity |
| Predicate | historicalBelligerent |
P81732
|
FINISHED |
| Object | British East India Company |
—
|
NE NERFINISHED |
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: British East India Company | Statement: [Sholinghur, historicalBelligerent, British East India Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalBelligerent Context triple: [Sholinghur, historicalBelligerent, British East India Company]
-
A.
opponentInHistoricalConflict
chosen
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
B.
partOfHistoricalConflict
Indicates that one entity participated in, belonged to, or was involved as a component of a larger historical conflict or war.
-
C.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
-
D.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
E.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
- F. None of above.
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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a017a360f088190acd5933aa353e763 |
completed | May 11, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_6a0179d3f78c8190b1d2e8829619fa54 |
completed | May 11, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:14 p.m.