Triple

T28500867
Position Surface form Disambiguated ID Type / Status
Subject De'ang E721224 entity
Predicate teaCultureSignificance P84689 FINISHED
Object tea used in rituals and social exchange 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: tea used in rituals and social exchange | Statement: [De'ang, teaCultureSignificance, tea used in rituals and social exchange]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: teaCultureSignificance
Context triple: [De'ang, teaCultureSignificance, tea used in rituals and social exchange]
  • A. teaCulture chosen
    Indicates the relationship in which practices, rituals, and social norms surrounding the preparation and consumption of tea are shared, expressed, or maintained.
  • B. coffeeSymbolizes
    Indicates that coffee is used as a symbol or representation of a particular idea, feeling, or concept.
  • C. teaCategory
    Indicates that one item is classified as belonging to a particular category or type of tea.
  • D. teaType
    Indicates the specific variety or category of tea associated with an entity.
  • E. teaIndustryDevelopedUnder
    Indicates that the tea industry grew, expanded, or was significantly shaped under the influence, control, or conditions provided by a particular authority, period, or context.
  • 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_69f01a5afdac8190ac6e72d5c100bd58 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64f43700c8190b16ba41e7a6b4809 completed May 2, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69f64cb0d8008190912e1430cfaf92aa completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 3:06 a.m.