Triple

T26803625
Position Surface form Disambiguated ID Type / Status
Subject Banga E671164 entity
Predicate relatedToModernRegion P25757 FINISHED
Object 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: Bengal | Statement: [Banga, relatedToModernRegion, Bengal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedToModernRegion
Context triple: [Banga, relatedToModernRegion, Bengal]
  • A. modernRegion chosen
    Indicates that an entity is located within or associated with a contemporary, present-day geographic or administrative region.
  • B. historicalRegionNowInCountry
    Indicates that a historical region is currently located within the borders or jurisdiction of a specified modern country.
  • C. historicalRegionCorrespondsTo
    Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
  • D. historicallyAssociatedWithModernCountry
    Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
  • E. locatedInModernAdministrativeRegion
    Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
  • 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_69fed83b1d188190a318b0ad3003200a completed May 9, 2026, 6:46 a.m.
PD Predicate disambiguation batch_69fed78e03548190b6e6ad93ae8d131d completed May 9, 2026, 6:43 a.m.
Created at: April 27, 2026, 4:24 a.m.