Triple
T31674643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 23 of the United Nations Charter |
E808365
|
entity |
| Predicate | currentlySpecifiesNumberOfMembers |
P9078
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Article 23 of the United Nations Charter, currentlySpecifiesNumberOfMembers, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentlySpecifiesNumberOfMembers Context triple: [Article 23 of the United Nations Charter, currentlySpecifiesNumberOfMembers, 15]
-
A.
numberOfMembersDeterminedBy
Indicates that the quantity of members in one entity is defined or constrained by another entity or factor.
-
B.
hasCurrentNumberOfMembers
chosen
Indicates the current count of members associated with a given entity.
-
C.
originalNumberOfMembers
Indicates the initial total count of members in a group or organization before any changes such as additions or removals.
-
D.
lastKnownNumberOfMembers
Indicates the most recently recorded count of members associated with an entity.
-
E.
traditionalNumberOfMembers
Indicates the customary or historically typical number of members associated with an entity or group.
- 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_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 30, 2026, 11:02 p.m.