Triple

T23194589
Position Surface form Disambiguated ID Type / Status
Subject Canton System E579839 entity
Predicate tradeRestrictedFrom P111719 FINISHED
Object other Chinese ports 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: other Chinese ports | Statement: [Canton System, tradeRestrictedFrom, other Chinese ports]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tradeRestrictedFrom
Context triple: [Canton System, tradeRestrictedFrom, other Chinese ports]
  • A. prohibitedTradeWith chosen
    Indicates that one entity is forbidden or restricted from engaging in trade or commercial exchange with another entity.
  • B. politicalRestriction
    Indicates that there are limitations or prohibitions imposed on an entity’s political activities, rights, or participation.
  • C. eligibilityRestrictedBy
    Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
  • D. productionRestrictedTo
    Indicates that the production or manufacture of something is limited or confined to a specified location, entity, or set of conditions.
  • E. oftenRestrictedTo
    Indicates that the use, occurrence, or applicability of something is frequently limited to a particular subset, context, or condition.
  • 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_69e24600eed08190bd7e5295653a1503 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18fda64cc8190aeb5ccd8d8d20858 completed April 29, 2026, 4:58 a.m.
PD Predicate disambiguation batch_69ef8a041c0081909afb670d17a5aaba completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4:06 p.m.