Triple
T1976666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔡崇信 |
E42929
|
entity |
| Predicate | 与国家或地区的关系 |
P835
|
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.
diplomaticRelation
Indicates a formal relationship of negotiation, communication, or representation between political entities, typically states or governments.
-
B.
foreignRelationsManagedBy
Indicates that the responsibility for conducting or overseeing a party’s foreign relations is held by a specified managing entity.
-
C.
diplomaticRelationContext
Indicates the contextual circumstances, conditions, or framework within which a diplomatic relationship between entities exists or is conducted.
-
D.
relationshipWithUN
Indicates the existence or nature of a formal or informal association, affiliation, or interaction between an entity and the United Nations.
-
E.
relatedCountry
chosen
Indicates that there is a relevant or associated relationship between an entity and a specified country, without specifying the exact nature of that relationship.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f9a87c8190816db3888787ad76 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.