Triple

T20677009
Position Surface form Disambiguated ID Type / Status
Subject Chinese Taipei flag (modified form) E508184 entity
Predicate replacesFlag P113059 FINISHED
Object flag of the Republic of China 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: flag of the Republic of China | Statement: [Chinese Taipei flag (modified form), replacesFlag, flag of the Republic of China]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacesFlag
Context triple: [Chinese Taipei flag (modified form), replacesFlag, flag of the Republic of China]
  • A. reflaggedAs chosen
    Indicates that an entity has been assigned a new flag, status, or label, replacing or superseding its previous one.
  • B. seeksToReplace
    Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
  • C. replacementName
    Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
  • D. formerFlag
    Indicates that an entity previously served as a flag of another entity but no longer holds that status.
  • E. replacedBecause
    Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
  • 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_69e0b4c1164881909a3bf1e3ddb2bc32 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6bea24f288190928f828e5f567257 completed April 21, 2026, 12:02 a.m.
PD Predicate disambiguation batch_69e5c03caee881908be4dd25796a03d5 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 11:44 a.m.