Triple

T11377748
Position Surface form Disambiguated ID Type / Status
Subject Maheshwar E269512 entity
Predicate weavingCommunity P98985 FINISHED
Object local weavers of Maheshwar 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: local weavers of Maheshwar | Statement: [Maheshwar, weavingCommunity, local weavers of Maheshwar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: weavingCommunity
Context triple: [Maheshwar, weavingCommunity, local weavers of Maheshwar]
  • A. weavingCenter
    Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
  • B. hasWeave
    Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
  • C. craftGuild
    Indicates that an entity is a member of, affiliated with, or governed by a particular craft guild organization.
  • D. traditionalCraft
    Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
  • E. collaboratingCommunity
    Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d800160a1c81909d115bf89fe54a49 completed April 9, 2026, 7:37 p.m.
PD Predicate disambiguation batch_69d7e7022d508190996f9be0847c2b41 completed April 9, 2026, 5:50 p.m.
PDg Predicate description generation batch_69d80010712c819089ea2e31e664abe1 completed April 9, 2026, 7:37 p.m.
Created at: April 8, 2026, 9:33 p.m.