Triple
T30964209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTR |
E788904
|
entity |
| Predicate | issuerControlledBy |
P97456
|
FINISHED |
| Object | Government of the People’s Republic of China |
—
|
NE NERFINISHED |
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: Government of the People’s Republic of China | Statement: [PTR, issuerControlledBy, Government of the People’s Republic of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerControlledBy Context triple: [PTR, issuerControlledBy, Government of the People’s Republic of China]
-
A.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
B.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
C.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
D.
isUnderControlOf
chosen
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
E.
issuerOperatesService
Indicates that an issuer is responsible for operating or running a particular service.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 8:54 p.m.