Triple
T10923085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collective Security Treaty |
E257994
|
entity |
| Predicate | allowsWithdrawal |
P72242
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Collective Security Treaty, allowsWithdrawal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsWithdrawal Context triple: [Collective Security Treaty, allowsWithdrawal, yes]
-
A.
canWithdraw
chosen
Indicates that an entity has the permission or ability to withdraw something (such as funds, items, or resources) from a source or account.
-
B.
withdrawalType
Indicates the specific method or category by which a withdrawal is carried out in a given context.
-
C.
hasWithdrawalRisk
Indicates that discontinuing or reducing something is associated with a risk of withdrawal effects or adverse reactions.
-
D.
canWithdrawConfidenceFrom
Indicates that an entity has the authority or ability to revoke or remove its previously given confidence or support from another entity.
-
E.
withdrawalEnd
Indicates the point in time or condition at which a withdrawal process or right comes to an end.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708e3fd881908da10f24a856364c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.