Triple
T3217068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengal Subah |
E67421
|
entity |
| Predicate | eventSignificance |
P259
|
FINISHED |
| Object | beginning of British political control in Bengal |
—
|
LITERAL FINISHED |
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: beginning of British political control in Bengal | Statement: [Bengal Subah, eventSignificance, beginning of British political control in Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventSignificance Context triple: [Bengal Subah, eventSignificance, beginning of British political control in Bengal]
-
A.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
eventInfluencedBy
Indicates that an event occurs or unfolds in a way that is causally or significantly affected by another entity, factor, or prior event.
-
C.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
D.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0ae494819093d39c367facde27 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.