Triple
T31674666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 23 of the United Nations Charter |
E808365
|
entity |
| Predicate | permanentMembersMentioned |
P63729
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Article 23 of the United Nations Charter, permanentMembersMentioned, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentMembersMentioned Context triple: [Article 23 of the United Nations Charter, permanentMembersMentioned, China]
-
A.
hasPermanentMembers
Indicates that certain members of a group or organization hold ongoing, non-temporary membership status.
-
B.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
C.
claimedMembers
Indicates that an entity asserts or reports that certain other entities are its members or belong to it.
-
D.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
E.
mentionedWith
chosen
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:02 p.m.