Triple
T20024147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 105-292 |
E494932
|
entity |
| Predicate | typeOfSanctionsAuthorized |
P18137
|
FINISHED |
| Object | diplomatic measures |
—
|
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: diplomatic measures | Statement: [Public Law 105-292, typeOfSanctionsAuthorized, diplomatic measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSanctionsAuthorized Context triple: [Public Law 105-292, typeOfSanctionsAuthorized, diplomatic measures]
-
A.
typeOfSanction
chosen
Indicates the specific category or kind of sanction that is applied in a given situation.
-
B.
isSanctionedBy
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
C.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
-
D.
canBeSanctionedFor
Indicates that an entity is subject to penalties or disciplinary measures as a consequence of a specified action, behavior, or condition.
-
E.
coSanctions
Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628b6b7c81909a660fbec9c92295 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.