Triple
T23881324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 辛丑条约 |
E600207
|
entity |
| Predicate | 外交条款 |
P42068
|
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.
diplomaticPolicy
chosen
Indicates the stance, strategy, or set of guiding principles an entity adopts in managing its diplomatic relations and interactions with others.
-
C.
diplomaticActivity
Indicates engagement in formal or informal diplomatic actions or interactions between parties, such as negotiations, consultations, or representation.
-
D.
diplomaticRelationContext
Indicates the contextual circumstances, conditions, or framework within which a diplomatic relationship between entities exists or is conducted.
-
E.
politicalRelation
Indicates a relationship between entities that involves political alignment, influence, affiliation, conflict, or cooperation within a political context.
- 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.