Triple
T26803627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banga |
E671164
|
entity |
| Predicate | relatedToModernIndianState |
P138136
|
FINISHED |
| Object | West Bengal |
—
|
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: West Bengal | Statement: [Banga, relatedToModernIndianState, West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToModernIndianState Context triple: [Banga, relatedToModernIndianState, West Bengal]
-
A.
isPartOfIndianState
Indicates that one entity is a constituent part or subdivision of an Indian state.
-
B.
containsFormerPrincelyState
Indicates that a geopolitical entity includes within its boundaries an area that was once a princely state.
-
C.
historicallyAssociatedWithModernCountry
chosen
Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
-
D.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
E.
integratedIntoIndianUnionAs
Indicates that an entity (such as a region or princely state) was formally incorporated into the political and administrative framework of the Indian Union.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 27, 2026, 4:24 a.m.