Triple
T11045193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Joint Declaration 1984 |
E261118
|
entity |
| Predicate | UNTreatySeriesNumber |
P38246
|
FINISHED |
| Object | UNTS 1399, p. 33 |
—
|
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: UNTS 1399, p. 33 | Statement: [Hong Kong Joint Declaration 1984, UNTreatySeriesNumber, UNTS 1399, p. 33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNTreatySeriesNumber Context triple: [Hong Kong Joint Declaration 1984, UNTreatySeriesNumber, UNTS 1399, p. 33]
-
A.
treatyNumber
chosen
Indicates the specific identifying number assigned to a treaty within a legal or diplomatic framework.
-
B.
treatyPartNumber
Indicates the specific part or section number within a treaty to which something (e.g., a provision, reference, or citation) is related.
-
C.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
D.
treatyName
Indicates the formal name or title assigned to a specific treaty.
-
E.
treatyAlsoKnownAs
Indicates that a treaty is referred to by an alternative name or alias.
- 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.