Triple
T14916653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention for the Extension of Hong Kong Territory |
E371399
|
entity |
| Predicate | leaseEndYear |
P84092
|
FINISHED |
| Object | 1997 |
—
|
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 | Statement: [Convention for the Extension of Hong Kong Territory, leaseEndYear, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseEndYear Context triple: [Convention for the Extension of Hong Kong Territory, leaseEndYear, 1997]
-
A.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
B.
indentureEndYear
chosen
Indicates the calendar year in which an indenture (a formal legal or contractual agreement) is scheduled to terminate or has terminated.
-
C.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
D.
travelEndYear
Indicates the year in which a travel event or journey concludes.
-
E.
saleYear
Indicates the calendar year in which a sale transaction took place.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:31 a.m.