Triple

T38499829
Position Surface form Disambiguated ID Type / Status
Subject Legislative Council (India) E919795 entity
Predicate historicalStatesWithCouncil P203924 FINISHED
Object Tamil Nadu E33506 NE 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: Tamil Nadu | Statement: [Legislative Council (India), historicalStatesWithCouncil, Tamil Nadu]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalStatesWithCouncil
Context triple: [Legislative Council (India), historicalStatesWithCouncil, Tamil Nadu]
  • A. currentStatesWithCouncil
    Indicates that certain states presently have an established council functioning within their governmental or organizational structure.
  • B. governingBodyHistory
    Indicates the sequence of past governing bodies or authorities that have held official control or oversight over an entity across time.
  • C. historicalState
    Indicates that an entity existed in a particular state or condition during a specified time in the past.
  • D. hasHistoricalPolity
    Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
  • E. hasParliamentaryHistory
    Indicates that an entity possesses a record or background of involvement, activity, or events within a parliamentary context.
  • F. None of above. chosen

Provenance (5 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_69f76e9ddd4481908f8c04439d848f9d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a02f2d6f35481909829d4ec710dcb0f completed May 12, 2026, 9:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a41e0222e5c81909ec8e912dee4cf0b completed June 29, 2026, 3:01 a.m.
PD Predicate disambiguation batch_6a02f15a2460819080cb4be5b50221d0 completed May 12, 2026, 9:22 a.m.
PDg Predicate description generation batch_6a02f2d64b28819095578e5317c764b5 completed May 12, 2026, 9:28 a.m.
Created at: May 3, 2026, 4:31 p.m.