Triple
T14318876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLR |
E355027
|
entity |
| Predicate | representsCountryUNMembership |
P644
|
FINISHED |
| Object | United Nations member state |
—
|
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: United Nations member state | Statement: [BLR, representsCountryUNMembership, United Nations member state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCountryUNMembership Context triple: [BLR, representsCountryUNMembership, United Nations member state]
-
A.
UNMemberState
chosen
Indicates that a country is a recognized member state of the United Nations.
-
B.
shareUNMembership
Indicates that the entities are both member states of the United Nations at the same time.
-
C.
recognizedByMajorityOfUNMembersAsPartOf
Indicates that an entity is widely acknowledged by a majority of United Nations member states as belonging to, or being a constituent part of, another entity.
-
D.
dateOfUNMembership
Indicates the specific date on which an entity officially became a member of the United Nations.
-
E.
hasUNStatus
Indicates that an entity holds a particular formal status or recognition within the United Nations system.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.