Triple
T23777365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non-SDN Iran Sanctions Act List |
E587710
|
entity |
| Predicate | shortOf |
P146179
|
FINISHED |
| Object | full Specially Designated National status |
—
|
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: full Specially Designated National status | Statement: [Non-SDN Iran Sanctions Act List, shortOf, full Specially Designated National status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortOf Context triple: [Non-SDN Iran Sanctions Act List, shortOf, full Specially Designated National status]
-
A.
wasShortened
Indicates that something has been made shorter in length, duration, or extent compared to its original form.
-
B.
isShort
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
-
C.
notSufficientFor
chosen
Indicates that the presence or occurrence of one condition does not by itself guarantee or bring about the other condition.
-
D.
shortcomings
Indicates that an entity has flaws, deficiencies, or limitations in its qualities, performance, or behavior.
-
E.
hasShort
Indicates that an entity possesses or is characterized by something of short length or duration.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46d55588190ad9c7e3c729b6b17 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.