Triple
T14917029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British informal empire in China |
E371406
|
entity |
| Predicate | effectivelyEndedWith |
P27991
|
FINISHED |
| Object | establishment of the People’s Republic of China |
—
|
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: establishment of the People’s Republic of China | Statement: [British informal empire in China, effectivelyEndedWith, establishment of the People’s Republic of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectivelyEndedWith Context triple: [British informal empire in China, effectivelyEndedWith, establishment of the People’s Republic of China]
-
A.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
B.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
C.
concludedWith
chosen
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
D.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
-
E.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
- 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_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. |
Created at: April 10, 2026, 2:32 a.m.