Triple

T35038310
Position Surface form Disambiguated ID Type / Status
Subject Syro-Malabar eparchies E1010989 entity
Predicate areHistoricallyRootedIn P34787 FINISHED
Object Kerala 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: Kerala | Statement: [Syro-Malabar eparchies, areHistoricallyRootedIn, Kerala]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: areHistoricallyRootedIn
Context triple: [Syro-Malabar eparchies, areHistoricallyRootedIn, Kerala]
  • A. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • B. historicallyBasedOn
    Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
  • C. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • D. historicallyNativeTo
    Indicates that an entity has been originally or traditionally present in, or originating from, a particular place or region over a significant period in history.
  • E. hasAncestralRoots chosen
    Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
  • 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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7858f4eac8190a71bc6fddd380cda completed May 3, 2026, 5:27 p.m.
PD Predicate disambiguation batch_69f7841812f081909d878955d114088e completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.