Triple
T12228408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 香港特別行政區行政長官 |
E291412
|
entity |
| Predicate | 任命機關 |
P6733
|
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.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
B.
appointedByOffice
chosen
Indicates that an entity attains its position or role through a formal appointment made by a specific office or official authority.
-
C.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
D.
appointedUnder
Indicates that one entity was formally given a position, role, or responsibility according to the authority, rules, or provisions established by another entity or legal framework.
-
E.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.