Triple

T23881329
Position Surface form Disambiguated ID Type / Status
Subject 辛丑条约 E600207 entity
Predicate 历史影响 P4749 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: [辛丑条约, 历史影响, 被视为近代中国主权丧失最严重的条约之一]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 历史影响
Context triple: [辛丑条约, 历史影响, 被视为近代中国主权丧失最严重的条约之一]
  • A. historicalImpact chosen
    Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
  • B. facedHistoricalImpact
    Indicates that an entity has experienced or been subjected to a significant influence, consequence, or change resulting from historical events or processes.
  • C. sharedHistoricalDynastyInfluence
    Indicates that two entities have both been significantly shaped or affected by the rule, legacy, or policies of the same historical dynasty.
  • D. hasCulturalImpact
    Indicates that one entity has influenced, shaped, or significantly affected the culture, values, practices, or artistic expressions of another.
  • E. heritageInfluence
    Indicates how one entity’s cultural, historical, or ancestral background affects or shapes another entity’s characteristics, behavior, or development.
  • 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_69e295318e148190b9979d8fc02e168f completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cc05e4d48190864fc47bdffa4ca9 completed April 29, 2026, 9:14 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:24 p.m.