Triple

T8654291
Position Surface form Disambiguated ID Type / Status
Subject Jangipur E205375 entity
Predicate hasAdministrativeSignificance P84156 FINISHED
Object yes 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: yes | Statement: [Jangipur, hasAdministrativeSignificance, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeSignificance
Context triple: [Jangipur, hasAdministrativeSignificance, yes]
  • A. hasAdministrativeType
    Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
  • B. administrativelyIn
    Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
  • C. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • D. usedForAdministrativePurposes
    Indicates that something is employed in managing, organizing, or overseeing official, institutional, or organizational activities and records.
  • E. administrativeFeature
    Indicates that one entity serves as an administrative or governance-related feature, function, or attribute associated with another entity.
  • F. None of above. chosen

Provenance (4 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_69ca8350897c819086cde7596fbe5fe7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc48432568819093b9a867b4f62b78 completed March 31, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69cc45619460819091e83ffdec99c865 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc473e44988190a3b02498e5fff668 completed March 31, 2026, 10:14 p.m.
Created at: March 30, 2026, 6:29 p.m.