Triple
T11045224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Joint Declaration 1984 |
E261118
|
entity |
| Predicate | handoverDateSpecified |
P14935
|
FINISHED |
| Object | 1997-07-01 |
—
|
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: 1997-07-01 | Statement: [Hong Kong Joint Declaration 1984, handoverDateSpecified, 1997-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handoverDateSpecified Context triple: [Hong Kong Joint Declaration 1984, handoverDateSpecified, 1997-07-01]
-
A.
dateHandedOver
Indicates the specific date on which something (such as an item, document, or responsibility) was formally transferred from one party to another.
-
B.
handoverToChinaDate
chosen
Indicates the date on which control, ownership, or responsibility is formally transferred to China.
-
C.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
D.
UNSeatTransferDate
Indicates the date on which a seat is transferred from one holder to another.
-
E.
supportsHandoverWith
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982f7e688190b3f0c249cd9b1a3e |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.