Triple
T12228433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 香港特別行政區行政長官 |
E291412
|
entity |
| Predicate | 設立依據 |
P125
|
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.
basisOfOrganization
Indicates that one entity serves as the foundational principle, criterion, or structure upon which another entity is organized or arranged.
-
B.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
C.
即位の根拠法
Indicates the legal basis or law that authorizes and legitimizes a person's accession to a position of rulership or throne.
-
D.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
E.
standingBasis
Indicates that one entity serves as the foundational reason, justification, or basis for another entity’s standing, status, or position in a given 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.