Triple
T29451559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino-Portuguese Joint Declaration |
E746987
|
entity |
| Predicate | definesStatusDuration |
P8729
|
FINISHED |
| Object | 50 years after 1999 |
—
|
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: 50 years after 1999 | Statement: [Sino-Portuguese Joint Declaration, definesStatusDuration, 50 years after 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStatusDuration Context triple: [Sino-Portuguese Joint Declaration, definesStatusDuration, 50 years after 1999]
-
A.
hasDurationType
Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
-
B.
hasOfficialDuration
chosen
Indicates the formally defined length of time associated with an event, process, or entity.
-
C.
durationInitial
Indicates the initial length of time associated with an event, state, or process at its starting point.
-
D.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
-
E.
durationDependsOn
Indicates that the length of time of one event or state is determined or influenced by another event, condition, or factor.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 3:32 p.m.