Triple
T37367361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kam Air |
E927747
|
entity |
| Predicate | subjectToSanctionsOrBans |
P59651
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kam Air, subjectToSanctionsOrBans, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToSanctionsOrBans Context triple: [Kam Air, subjectToSanctionsOrBans, true]
-
A.
isSanctionedBy
chosen
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
B.
coSanctionedBy
Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
-
C.
canBeSanctionedFor
Indicates that an entity is subject to penalties or disciplinary measures as a consequence of a specified action, behavior, or condition.
-
D.
coSanctionedWith
Indicates that an entity is subject to sanctions together with another entity, typically as part of the same sanctioning action or regime.
-
E.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:16 p.m.