Triple
T38575420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNSCOP |
E929387
|
entity |
| Predicate | excludedMemberState |
P34541
|
FINISHED |
| Object | United Kingdom |
—
|
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 Kingdom | Statement: [UNSCOP, excludedMemberState, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludedMemberState Context triple: [UNSCOP, excludedMemberState, United Kingdom]
-
A.
excludedOriginalMember
Indicates that an entity that was originally part of a group, set, or collection has been deliberately left out or removed from the current membership.
-
B.
isExcludedFor
Indicates that a particular entity is not allowed, applicable, or considered within a specified context, condition, or set.
-
C.
excludedFrom
chosen
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
D.
abstainingMemberState
Indicates that a member state is formally part of a decision-making body but chooses not to vote for or against a particular proposal or resolution.
-
E.
memberStatesAreMemberOf
Indicates that certain states belong to or hold membership in a particular organization, group, or union.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.