Triple

T5629428
Position Surface form Disambiguated ID Type / Status
Subject Mughal culture E147795 entity
Predicate hasTextileTradition P19423 FINISHED
Object luxury textiles 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: luxury textiles | Statement: [Mughal culture, hasTextileTradition, luxury textiles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTextileTradition
Context triple: [Mughal culture, hasTextileTradition, luxury textiles]
  • A. textileFeature
    Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
  • B. hasTraditionIn chosen
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • C. sharesDesignTraditionWith
    Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
  • D. traditionalDressVariant
    Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
  • E. typicalFabric
    Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
  • 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_69c00907bc8881909ed760d3ed73ef35 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c0223b1e54819099fe5fc84ed17a88 completed March 22, 2026, 5:09 p.m.
PD Predicate disambiguation batch_69c01b1f12ec8190b4b9d9ee31cabe19 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:40 p.m.