Triple
T11045179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Joint Declaration 1984 |
E261118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sino-British treaty |
C566
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Sino-British treaty Context triple: [Hong Kong Joint Declaration 1984, instanceOf, Sino-British treaty]
-
A.
treaty port concession
A treaty port concession is a designated area within a host country’s port where, under unequal treaty arrangements, foreign powers exercise special commercial, legal, and administrative privileges distinct from local jurisdiction.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
British overseas presence in China
The conceptual class "British overseas presence in China" encompasses the political, economic, military, and cultural activities, institutions, and influences established by Britain within Chinese territory from the early modern period through the end of formal imperial involvement.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
church treaty
A church treaty is a formal agreement between religious authorities and secular powers that defines the rights, privileges, and obligations of the church within a given political or legal framework.
- F. None of above.
Provenance (1 batch)
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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.