Triple

T29359541
Position Surface form Disambiguated ID Type / Status
Subject Lê dynasty E744546 entity
Predicate overthrow P28136 FINISHED
Object Tây Sơn rebellion NE NERFINISHED

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: Tây Sơn rebellion | Statement: [Lê dynasty, overthrow, Tây Sơn rebellion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: overthrow
Context triple: [Lê dynasty, overthrow, Tây Sơn rebellion]
  • A. overthrown
    Indicates that one entity has removed another from a position of power or authority, typically by force or political upheaval.
  • B. overthrewGovernment chosen
    Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
  • C. overthrownIn
    Indicates that one entity (such as a government, leader, or regime) was removed from power or defeated in a specific event, context, or time period represented by the other entity.
  • D. overthrownWithHelpOf
    Indicates that one entity was removed from power or defeated through the assistance, support, or intervention of another specified entity.
  • E. overthrowParticipants
    Indicates that the related entities are participants involved in carrying out or attempting an overthrow of an existing authority or regime.
  • 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669868ddc819095409dc5592c3e68 completed May 2, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 2:16 p.m.