Triple
T3456402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Party |
E72913
|
entity |
| Predicate | mayPerform |
P33310
|
FINISHED |
| Object | make reservations to a treaty |
—
|
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: make reservations to a treaty | Statement: [State Party, mayPerform, make reservations to a treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayPerform Context triple: [State Party, mayPerform, make reservations to a treaty]
-
A.
mayConduct
chosen
Indicates that one entity is permitted or authorized to carry out, perform, or execute a particular action, process, or operation on or with another entity.
-
B.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
-
C.
canBePerformed
Indicates that a particular action or activity is possible to carry out under given conditions or by a specified agent.
-
D.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
E.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa9837c8190aafd618c6af3446e |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.