Triple
T12228398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 香港特別行政區行政長官 |
E291412
|
entity |
| Predicate | 所屬地區 |
P64798
|
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.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
D.
locatedInRegionOfPrefecture
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional 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_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.