Triple
T29451571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino-Portuguese Joint Declaration |
E746987
|
entity |
| Predicate | UNRegistration |
P53863
|
FINISHED |
| Object | United Nations Treaty Series |
—
|
NE NERFINISHED |
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: United Nations Treaty Series | Statement: [Sino-Portuguese Joint Declaration, UNRegistration, United Nations Treaty Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNRegistration Context triple: [Sino-Portuguese Joint Declaration, UNRegistration, United Nations Treaty Series]
-
A.
UNMembershipStart
Indicates the date on which an entity first became a member of the United Nations.
-
B.
UNDesignation
Indicates that an entity has been formally assigned a specific status, role, or classification by the United Nations.
-
C.
UNMembershipSupport
Indicates support for a country’s admission to, or continued membership in, the United Nations.
-
D.
registrationFor
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
-
E.
officialRegisterOf
chosen
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
- 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.