Triple

T16731569
Position Surface form Disambiguated ID Type / Status
Subject Macartney Embassy of 1793 E406603 entity
Predicate ceremonialIssue P124422 FINISHED
Object kowtow controversy 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: kowtow controversy | Statement: [Macartney Embassy of 1793, ceremonialIssue, kowtow controversy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ceremonialIssue
Context triple: [Macartney Embassy of 1793, ceremonialIssue, kowtow controversy]
  • A. ceremonialStatus
    Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
  • B. ceremonialUse
    Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
  • C. ceremonialAssociation
    Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
  • D. isCeremonial
    Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
  • E. ceremonialSymbol
    Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
  • 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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e39c362bb88190921fab43d76c3ee8 completed April 18, 2026, 2:59 p.m.
PD Predicate disambiguation batch_69e319c807788190901250ab6e0ca55f completed April 18, 2026, 5:42 a.m.
PDg Predicate description generation batch_69e326b9e84881909a9166e65bd850d6 completed April 18, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:20 a.m.