Triple
T14917021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British informal empire in China |
E371406
|
entity |
| Predicate | limitedChinese |
P116667
|
FINISHED |
| Object | tariff autonomy |
—
|
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: tariff autonomy | Statement: [British informal empire in China, limitedChinese, tariff autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedChinese Context triple: [British informal empire in China, limitedChinese, tariff autonomy]
-
A.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
B.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
C.
hasChineseVersion
Indicates that an entity has a corresponding version or representation available in Chinese.
-
D.
usedChineseCharacters
Indicates that one entity employed or wrote using Chinese characters in relation to another entity or context.
-
E.
ChineseObjective
Indicates that an entity has an objective, goal, or target specifically related to China or the Chinese context.
- F. None of above. chosen
Provenance (4 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:32 a.m.