Triple
T29451551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino-Portuguese Joint Declaration |
E746987
|
entity |
| Predicate | setsHandoverDate |
P14935
|
FINISHED |
| Object | 1999-12-20 |
—
|
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: 1999-12-20 | Statement: [Sino-Portuguese Joint Declaration, setsHandoverDate, 1999-12-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsHandoverDate Context triple: [Sino-Portuguese Joint Declaration, setsHandoverDate, 1999-12-20]
-
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.
officeTransferredAt
Indicates the time or date at which an office (or official position) was transferred from one holder or location to another.
-
C.
dateOfTransfer
Indicates the specific date on which a transfer of something (such as ownership, rights, or funds) from one party to another takes place.
-
D.
handoverToChinaDate
chosen
Indicates the date on which control, ownership, or responsibility is formally transferred to China.
-
E.
UNSeatTransferDate
Indicates the date on which a seat is transferred from one holder to another.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b682f0c81908394f0f2f6ddc483 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:32 p.m.