Triple

T36339932
Position Surface form Disambiguated ID Type / Status
Subject 張學良 E894884 entity
Predicate surrenderedPower P29098 FINISHED
Object 宣佈東北易幟,接受南京國民政府領導 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: 宣佈東北易幟,接受南京國民政府領導 | Statement: [張學良, surrenderedPower, 宣佈東北易幟,接受南京國民政府領導]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: surrenderedPower
Context triple: [張學良, surrenderedPower, 宣佈東北易幟,接受南京國民政府領導]
  • A. surrenderedAfter
    Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
  • B. surrenderedIn chosen
    Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
  • C. typeOfSurrender
    Indicates the specific manner or category of surrender that characterizes how one party yields or gives up to another.
  • D. surrenderEvent
    Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
  • E. seizedPowerAfter
    Indicates that one entity took control or authority from another entity following a specified event or point in time.
  • 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_69f76e4e90148190b02fe52593c70b5b completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb3ff1b08190802b1063d55d3923 completed May 3, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69f7b9a611a081908dd6aec1df3f4d7f completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.